Feedback information transmission method and communication device

ABSTRACT

This application provides a method to improve resource utilization efficiency of an uplink control channel that carries feedback information. A terminal device receives one or more downlink channels carried in one or more first time units, the first time units belonging to in a time unit set; determines a second time unit for carrying feedback information corresponding to the downlink channels according to a first association relationship between the time unit set and the second time unit; determines a first codebook; and sends uplink control information including the first codebook in the second time unit. When one of the downlink channels is received in first time units that belong to a subset of the time unit set, and there is a second association relationship between the subset of the time unit set and the second time unit, the first codebook includes only feedback information corresponding to the downlink channel carried in the first time units in the subset.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent ApplicationNo. PCT/CN2019/072888, filed on Jan. 24, 2019, which claims priority toChinese Patent Application No. 201810150623.5, filed on Feb. 13, 2018,and Chinese Patent Application No. 201810302168.6, filed on Apr. 4,2018. All of the aforementioned patent applications are incorporated byreference in their entireties.

TECHNICAL FIELD

This application relates to the communication field, and morespecifically, to a feedback information transmission method and acommunication device.

BACKGROUND

Long term evolution (LTE) systems support semi-persistent codebookconfiguration. A codebook is determined based on the number of downlinksubframes in a semi-persistent downlink subframe set. For example, acodebook of acknowledgment (ACK)/negative acknowledgment (NACK)information includes feedback information corresponding to all downlinksubframes in a semi-persistent downlink subframe set. The downlinksubframes include downlink subframes for an actually scheduled physicaldownlink shared channel (PDSCH) or downlink subframes forsemi-persistent scheduling (SPS) release indication, and may alsoinclude unscheduled downlink subframes. An NACK is set in a position ofthe codebook corresponding to an unscheduled downlink subframe or adownlink subframe whose scheduling signaling is not received by aterminal device.

In existing LTE systems, fallback scheduling and codebook fallback aresupported for semi-persistent codebook configuration. Future fifthgeneration (5G) communication systems are different from the LTEsystems. Therefore, how to implement codebook fallback and fallbackscheduling mechanisms in the 5G systems to improve resource utilizationefficiency of an uplink control channel that carries feedbackinformation becomes a technical problem that needs to be resolved in the5G systems.

SUMMARY

Embodiments of this application provide a feedback informationtransmission method and a communication device, so as to improveresource utilization efficiency of an uplink control channel thatcarries feedback information.

According to a first aspect, a feedback information transmission methodis provided. The method includes: receiving, by a terminal device, atleast one piece of downlink information in at least one first time unitin a time unit set, where the time unit set is a set of at least onefirst time unit corresponding to at least one frequency domain unitconfigured for the terminal device;

determining, by the terminal device, a second time unit, where thesecond time unit is used to carry feedback information corresponding tothe at least one piece of downlink information, and there is a firstassociation relationship between the time unit set and the second timeunit;

determining, by the terminal device, a first codebook, where when firstdownlink information in a time unit subset meets a preset condition, thefirst codebook includes feedback information corresponding to the firstdownlink information, the first codebook does not include feedbackinformation corresponding to a specific time unit in the time unitsubset, the specific time unit is at least one first time unit in thetime unit set other than a first time unit in which the first downlinkinformation is located, the preset condition includes a first condition,the first condition is that the number of pieces of first downlinkinformation is equal to a first preset value, the time unit subset is asubset of the time unit set, and there is a second associationrelationship between the time unit subset and the second time unit; and

sending, by the terminal device, uplink control information in thesecond time unit, where the uplink control information carries the firstcodebook.

If the terminal device schedules a plurality of pieces of downlinkinformation in a plurality of time units in the time unit setcorresponding to the first association relationship, when the number ofpieces of downlink information corresponding to the second associationrelationship meets the first condition, codebook fallback can beperformed, thereby improving efficiency of utilizing, by a system, aresource of an uplink control channel that carries feedback information.

With reference to the first aspect, in some implementations of the firstaspect, the preset condition further includes a second condition, andthe second condition is that a value of indication information on adownlink control channel for dynamically scheduling the first downlinkinformation is a second preset value.

Optionally, the second preset value may be a downlink assignmentindicator (DAI) value.

With reference to the first aspect, in some implementations of the firstaspect, the preset condition further includes a third condition, and thethird condition is that the first time unit in which the first downlinkinformation is located is a first time unit in a specific time domainlocation in the time unit set.

With reference to the first aspect, in some implementations of the firstaspect, the preset condition further includes a fourth condition, andthe fourth condition is that the first downlink information is carriedin a primary frequency domain unit or a first secondary frequency domainunit in the at least one frequency domain unit.

With reference to the first aspect, in some implementations of the firstaspect, the preset condition may further include any one or more of thesecond condition, the third condition, and the fourth condition inaddition to the first condition. For example, the preset conditionfurther includes the second condition and the third condition inaddition to the first condition. Alternatively, the preset conditionfurther includes the second condition and the fourth condition inaddition to the first condition. This is not limited in thisapplication.

With reference to the first aspect, in some implementations of the firstaspect, when the number of pieces of the first downlink information inthe time unit subset does not meet the first condition, the firstcodebook includes feedback information corresponding to all first timeunits in the time unit set.

With reference to the first aspect, in some implementations of the firstaspect, the value of the indication information is set according to apredefined rule related to the time unit subset.

With reference to the first aspect, in some implementations of the firstaspect, for at least one first time unit that corresponds to each of theat least one frequency domain unit and that is in the first time unitsubset, the predefined rule is performing cumulative counting in asequential order of time units; or

for at least one first time unit that corresponds to the at least onefrequency domain unit and that is in the first time unit subset, thepredefined rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

A problem of inconsistent understanding between the terminal device anda network device that may be caused due to codebook fallback may beresolved through independent DAI cumulative counting in the time unitsubset.

With reference to the first aspect, in some implementations of the firstaspect, the at least one piece of downlink information further includessecond downlink information, where a downlink control channel forscheduling the second downlink information is a downlink control channelfor semi-persistent scheduling, and the first codebook further includesfeedback information corresponding to the second downlink information.

With reference to the first aspect, in some implementations of the firstaspect, the first association relationship is predefined according to astandard and/or configured for the terminal device by a network deviceby using radio resource control (RRC) signaling.

With reference to the first aspect, in some implementations of the firstaspect, the second association relationship is determined based on thedownlink control channel for dynamically scheduling the first downlinkinformation.

With reference to the first aspect, in some implementations of the firstaspect, before the determining, by the terminal device, a firstcodebook, the method further includes:

determining, by the terminal device, a semi-persistent codebook modefrom a plurality of candidate codebook modes, where the plurality ofcandidate codebook modes include a semi-persistent codebook mode and adynamic codebook mode.

With reference to the first aspect, in some implementations of the firstaspect, the first preset value is greater than or equal to 1, and whenthe first preset value is greater than 1, first downlink informationwhose number of pieces is equal to the first preset value carries sametransport block information.

With reference to the first aspect, in some implementations of the firstaspect, the first downlink information whose number of pieces is equalto the first preset value is scheduled by one downlink control channel.

With reference to the first aspect, in some implementations of the firstaspect, the first preset value is less than or equal to a third presetvalue, and the third preset value is determined based on a downlinkaggregation parameter configured by using higher layer signaling.

According to a second aspect, a feedback information transmission methodis provided. The method includes: sending, by a network device, at leastone piece of downlink information to a terminal device in at least onefirst time unit in a time unit set, where the time unit set is a set ofat least one first time unit corresponding to at least one frequencydomain unit configured for the terminal device;

determining, by the network device, a second time unit, where the secondtime unit is used to carry feedback information corresponding to the atleast one piece of downlink information, and there is a firstassociation relationship between the time unit set and the second timeunit; and

receiving, by the network device in the second time unit, uplink controlinformation sent by the terminal device, where the uplink controlinformation carries a first codebook, the first codebook is a firstcodebook when first downlink information in a time unit subset meets apreset condition, the first codebook includes feedback informationcorresponding to the first downlink information, the first codebook doesnot include feedback information corresponding to a specific time unitin the time unit subset, the specific time unit is at least one firsttime unit in the time unit set other than a first time unit in which thefirst downlink information is located, the preset condition includes afirst condition, the first condition is that the number of pieces offirst downlink information is equal to a first preset value, the timeunit subset is a subset of the time unit set, and there is a secondassociation relationship between the time unit subset and the secondtime unit.

The network device receives the first codebook sent by the terminaldevice. When the first downlink information in the time unit subsetmeets the preset condition, codebook fallback is performed for the firstcodebook, thereby improving efficiency of utilizing, by a system, aresource of an uplink control channel that carries feedback information.

With reference to the second aspect, in some implementations of thesecond aspect, the preset condition further includes a second condition,and the second condition is that a value of indication information on adownlink control channel for dynamically scheduling the first downlinkinformation is a second preset value.

With reference to the second aspect, in some implementations of thesecond aspect, the preset condition further includes a third condition,and the third condition is that the first time unit in which the firstdownlink information is located is a first time unit in a specific timedomain location in the time unit set.

With reference to the second aspect, in some implementations of thesecond aspect, the preset condition further includes a fourth condition,and the fourth condition is that the first downlink information iscarried in a primary frequency domain unit or a first secondaryfrequency domain unit in the at least one frequency domain unit.

With reference to the second aspect, in some implementations of thesecond aspect, the preset condition may further include any one or moreof the second condition, the third condition, and the fourth conditionin addition to the first condition. For example, the preset conditionfurther includes the second condition and the third condition inaddition to the first condition. Alternatively, the preset conditionfurther includes the second condition and the fourth condition inaddition to the first condition. This is not limited in thisapplication.

With reference to the second aspect, in some implementations of thesecond aspect, when the number of pieces of the first downlinkinformation in the time unit subset does not meet the first condition,the first codebook includes feedback information corresponding to allfirst time units in the time unit set.

With reference to the second aspect, in some implementations of thesecond aspect, the value of the indication information is set accordingto a predefined rule related to the time unit subset.

With reference to the second aspect, in some implementations of thesecond aspect, for at least one first time unit that corresponds to eachof the at least one frequency domain unit and that is in the first timeunit subset, the predefined rule is performing cumulative counting in asequential order of time units; or

for at least one first time unit that corresponds to the at least onefrequency domain unit and that is in the first time unit subset, thepredefined rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

A problem of inconsistent understanding between the terminal device andthe network device that may be caused due to codebook fallback may beresolved through independent DAI cumulative counting in the time unitsubset.

With reference to the second aspect, in some implementations of thesecond aspect, the at least one piece of downlink information furtherincludes second downlink information, where a downlink control channelfor scheduling the second downlink information is a downlink controlchannel for semi-persistent scheduling, and the first codebook furtherincludes feedback information corresponding to the second downlinkinformation.

With reference to the second aspect, in some implementations of thesecond aspect, the first association relationship is predefinedaccording to a standard and/or configured for the terminal device by thenetwork device by using RRC signaling.

With reference to the second aspect, in some implementations of thesecond aspect, the second association relationship is indicated by thedownlink control channel for dynamically scheduling the first downlinkinformation.

With reference to the second aspect, in some implementations of thesecond aspect, before the receiving, by the network device in the secondtime unit, uplink control information sent by the terminal device, themethod further includes:

determining, by the network device, a semi-persistent codebook mode froma plurality of candidate codebook modes, where the plurality ofcandidate codebook modes include a semi-persistent codebook mode and adynamic codebook mode; and

configuring, by the network device, the semi-persistent codebook modefor the terminal device by using signaling.

With reference to the second aspect, in some implementations of thesecond aspect, the first preset value is greater than or equal to 1, andwhen the first preset value is greater than 1, first downlinkinformation whose number of pieces is equal to the first preset valuecarries same transport block information.

With reference to the second aspect, in some implementations of thesecond aspect, the first downlink information whose number of pieces isequal to the first preset value is scheduled by one downlink controlchannel.

With reference to the second aspect, in some implementations of thesecond aspect, the first preset value is less than or equal to a thirdpreset value, and the third preset value is determined based on adownlink aggregation parameter configured by using higher layersignaling.

With reference to the first aspect and the second aspect, in somepossible implementations, the at least one piece of downlink informationis downlink information of dynamic scheduling, and specifically, mayinclude semi-persistent scheduling (SPS) release indication or adynamically scheduled downlink data channel. A dynamically scheduleddownlink data channel is dynamically scheduled through a downlinkcontrol channel, where dynamic scheduling means that each transmissionof a downlink data channel needs to be scheduled through a correspondingdownlink control channel.

A semi-persistently scheduled downlink data channel is scheduled througha semi-persistent downlink control channel. After control information issent once through the semi-persistent downlink control channel, acorresponding semi-persistent downlink data channel may be always sentaccording to a preconfigured sending cycle, with no need to send thesemi-persistent downlink control channel each time. Semi-persistentdownlink scheduling may be released through a specific downlink controlchannel. A downlink control channel used to implement release indicationof the semi-persistent downlink scheduling is usually not used toschedule a downlink data channel.

However, the terminal device also needs to feed back ACK/NACK feedbackinformation for the downlink control channel.

With reference to the first aspect or the second aspect, in somepossible implementations, a time unit may be at least one of a slot, amini-slot, and a subframe.

With reference to the first aspect or the second aspect, in somepossible implementations, a frequency domain unit may be a carrier or acarrier bandwidth part (BWP).

With reference to the first aspect or the second aspect, in somepossible implementations, the first time unit is a downlink time unit ora flexible time unit.

With reference to the first aspect or the second aspect, in somepossible implementations, the second time unit is an uplink time unit ora flexible time unit.

With reference to the first aspect or the second aspect, in somepossible implementations, a downlink control channel for fallbackscheduling has at least one of the following characteristics:

the downlink control channel is used for data scheduling performedbefore RRC establishment; and none of values of all fields in thecontrol channel, for example, a time domain resource allocation field, aDAI field, and a BWP indication field, may be configured by using RRCdedicated signaling.

With reference to the first aspect or the second aspect, in somepossible implementations, the terminal device may be configured todetect a downlink control channel for non-fallback scheduling. Thecontrol channel has at least one of the following characteristics:

the downlink control channel is used for data scheduling performed afterRRC establishment; and a value of at least one field in the controlchannel, for example, a time domain resource allocation field, a DAIfield, and a BWP indication field, may be configured by using RRCdedicated signaling.

With reference to the first aspect or the second aspect, in somepossible implementations, first indication information included on thedownlink control channel for dynamically scheduling the first downlinkinformation is a DAI field, and the preset value is preferably DAI=1 ora value indicated by a state ‘00’ of the DAI field.

With reference to the first aspect or the second aspect, in somepossible implementations, in the dynamic codebook mode, the terminaldevice determines a second codebook of feedback information, where thesecond codebook includes feedback information corresponding to anactually scheduled first time unit in the time unit set.

With reference to the first aspect or the second aspect, in somepossible implementations, before the terminal device sends the feedbackinformation in the second time unit based on the first codebook, theterminal device determines a target resource set of an uplink controlchannel, and determines a target resource of the uplink control channelfrom the target resource set. The terminal device sends the uplinkcontrol information on the target resource in the second time unit,where the uplink control information carries the first codebook.

With reference to the first aspect or the second aspect, in somepossible implementations, for example, when the number of pieces of thefirst downlink information in the at least one piece of downlinkinformation is equal to the first preset value (for example, the firstpreset value is 1) or when the foregoing other conditions are met, thatis, the first codebook in this case is a fallback codebook, the targetresource set is a first resource set, and a codebook size of the firstcodebook corresponding to the first resource set is less than or equalto 2.

With reference to the first aspect or the second aspect, in somepossible implementations, when the number of pieces of the firstdownlink information in the at least one piece of downlink informationis not the first preset value, the target resource set is a secondresource set, and a codebook size of the first codebook corresponding tothe second resource set is greater than 2. In this case, the firstcodebook is a non-fallback codebook or a normal semi-persistentcodebook. In this case, the terminal device sends the first codebook ofthe feedback information on a second target resource in the secondresource set.

According to a third aspect, a communication device for transmittingfeedback information is provided The device includes: a transceiverunit, configured to receive at least one piece of downlink informationin at least one first time unit in a time unit set, where the time unitset is a set of at least one first time unit corresponding to at leastone frequency domain unit configured for a terminal device; and

a processing unit, configured to determine a second time unit, where thesecond time unit is used to carry feedback information corresponding tothe at least one piece of downlink information, and there is a firstassociation relationship between the time unit set and the second timeunit; and configured to determine a first codebook, where when firstdownlink information in a time unit subset meets a preset condition, thefirst codebook includes feedback information corresponding to the firstdownlink information, the first codebook does not include feedbackinformation corresponding to a specific time unit in the time unitsubset, the specific time unit is at least one first time unit in thetime unit set other than a first time unit in which the first downlinkinformation is located, the preset condition includes a first condition,the first condition is that the number of pieces of first downlinkinformation is equal to a first preset value, the time unit subset is asubset of the time unit set, and there is a second associationrelationship between the time unit subset and the second time unit;where

the transceiver unit is configured to send uplink control information inthe second time unit, where the uplink control information carries thefirst codebook.

In a semi-persistent codebook mode, when the communication device fortransmitting feedback information schedules a plurality of pieces ofdownlink information in at least one time unit for sending the feedbackinformation, specifically, in a plurality of time units in the time unitset corresponding to the first association relationship, when the numberof pieces of downlink information corresponding to the secondassociation relationship meets the first condition, codebook fallbackcan be performed, thereby improving efficiency of utilizing, by asystem, a resource of an uplink control channel that carries feedbackinformation.

With reference to the third aspect, in some implementations of the thirdaspect, the preset condition further includes a second condition, andthe second condition is that a value of indication information on adownlink control channel for dynamically scheduling the first downlinkinformation is a second preset value.

With reference to the third aspect, in some implementations of the thirdaspect, the preset condition further includes a third condition, and thethird condition is that the first time unit in which the first downlinkinformation is located is a first time unit in a specific time domainlocation in the time unit set.

With reference to the third aspect, in some implementations of the thirdaspect, the preset condition further includes a fourth condition, andthe fourth condition is that the first downlink information is carriedin a primary frequency domain unit or a first secondary frequency domainunit in the at least one frequency domain unit.

With reference to the third aspect, in some implementations of the thirdaspect, when the number of pieces of the first downlink information inthe time unit subset does not meet the first condition, the firstcodebook includes feedback information corresponding to all first timeunits in the time unit set.

With reference to the third aspect, in some implementations of the thirdaspect, the value of the indication information is set according to apredefined rule related to the time unit subset.

With reference to the third aspect, in some implementations of the thirdaspect, for at least one first time unit that corresponds to each of theat least one frequency domain unit and that is in the first time unitsubset, the predefined rule is performing cumulative counting in asequential order of time units; or

for at least one first time unit that corresponds to the at least onefrequency domain unit and that is in the first time unit subset, thepredefined rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

A problem of inconsistent understanding between the terminal device anda network device that may be caused due to codebook fallback may beresolved through independent DAI cumulative counting in the time unitsubset.

With reference to the third aspect, in some implementations of the thirdaspect, the at least one piece of downlink information further includessecond downlink information, where a downlink control channel forscheduling the second downlink information is a downlink control channelfor semi-persistent scheduling, and the first codebook further includesfeedback information corresponding to the second downlink information.

With reference to the third aspect, in some implementations of the thirdaspect, the first association relationship is predefined according to astandard and/or configured for the terminal device by a network deviceby using RRC signaling.

With reference to the third aspect, in some implementations of the thirdaspect, the second association relationship is determined based on thedownlink control channel for dynamic scheduling.

With reference to the third aspect, in some implementations of the thirdaspect, the processing unit is further configured to determine asemi-persistent codebook mode from a plurality of candidate codebookmodes, where the plurality of candidate codebook modes include asemi-persistent codebook mode and a dynamic codebook mode.

With reference to the third aspect, in some implementations of the thirdaspect, the first preset value is greater than or equal to 1, and whenthe first preset value is greater than 1, first downlink informationwhose number of pieces is equal to the first preset value carries sametransport block information.

With reference to the third aspect, in some implementations of the thirdaspect, the first downlink information whose number of pieces is equalto the first preset value is scheduled by one downlink control channel.

With reference to the third aspect, in some implementations of the thirdaspect, the first preset value is less than or equal to a third presetvalue, and the third preset value is determined based on a downlinkaggregation parameter configured by using higher layer signaling.

According to a fourth aspect, a communication device for transmittingfeedback information is provided. The device includes: a transceiverunit, configured to send at least one piece of downlink information to aterminal device in at least one first time unit in a time unit set,where the time unit set is a set of at least one first time unitcorresponding to at least one frequency domain unit configured for theterminal device; and

a processing unit, configured to determine a second time unit, where thesecond time unit is used to carry feedback information corresponding tothe at least one piece of downlink information, and there is a firstassociation relationship between the time unit set and the second timeunit; where

the transceiver unit is configured to receive, in the second time unit,uplink control information sent by the terminal device, where the uplinkcontrol information carries a first codebook, the first codebook is afirst codebook when first downlink information in a time unit subsetmeets a preset condition, the first codebook includes feedbackinformation corresponding to the first downlink information, the firstcodebook does not include feedback information corresponding to aspecific time unit in the time unit subset, the specific time unit is atleast one first time unit in the time unit set other than a first timeunit in which the first downlink information is located, the presetcondition includes a first condition, the first condition is that thenumber of pieces of first downlink information is equal to a firstpreset value, the time unit subset is a subset of the time unit set, andthere is a second association relationship between the time unit subsetand the second time unit.

A network device receives the first codebook sent by the terminaldevice. When the first downlink information in the time unit subsetmeets the preset condition, codebook fallback is performed for the firstcodebook, thereby improving efficiency of utilizing, by a system, aresource of an uplink control channel that carries feedback information.

With reference to the fourth aspect, in some implementations of thefourth aspect, the preset condition further includes a second condition,and the second condition is that a value of indication information on adownlink control channel for dynamically scheduling the first downlinkinformation is a second preset value.

With reference to the fourth aspect, in some implementations of thefourth aspect, the preset condition further includes a third condition,and the third condition is that the first time unit in which the firstdownlink information is located is a first time unit in a specific timedomain location in the time unit set.

With reference to the fourth aspect, in some implementations of thefourth aspect, the preset condition further includes a fourth condition,and the fourth condition is that the first downlink information iscarried in a primary frequency domain unit or a first secondaryfrequency domain unit in the at least one frequency domain unit.

With reference to the fourth aspect, in some implementations of thefourth aspect, when the number of pieces of the first downlinkinformation in the time unit subset does not meet the first condition,the first codebook includes feedback information corresponding to allfirst time units in the time unit set.

With reference to the fourth aspect, in some implementations of thefourth aspect, the value of the indication information is set accordingto a predefined rule related to the time unit subset.

With reference to the fourth aspect, in some implementations of thefourth aspect, for at least one first time unit that corresponds to eachof the at least one frequency domain unit and that is in the first timeunit subset, the predefined rule is performing cumulative counting in asequential order of time units; or

for at least one first time unit that corresponds to the at least onefrequency domain unit and that is in the first time unit subset, thepredefined rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

A problem of inconsistent understanding between the terminal device andthe network device that may be caused due to codebook fallback may beresolved through independent DAI cumulative counting in a time unitsubset.

With reference to the fourth aspect, in some implementations of thefourth aspect, the at least one piece of downlink information furtherincludes second downlink information, where a downlink control channelfor scheduling the second downlink information is a downlink controlchannel for semi-persistent scheduling, and the first codebook furtherincludes feedback information corresponding to the second downlinkinformation.

With reference to the fourth aspect, in some implementations of thefourth aspect, the first association relationship is predefinedaccording to a standard and/or configured for the terminal device by thenetwork device by using RRC signaling.

With reference to the fourth aspect, in some implementations of thefourth aspect, the second association relationship is indicated by thedownlink control channel for dynamically scheduling the first downlinkinformation.

With reference to the fourth aspect, in some implementations of thefourth aspect, the processing unit is further configured to:

determine a semi-persistent codebook mode from a plurality of candidatecodebook modes, where the plurality of candidate codebook modes includea semi-persistent codebook mode and a dynamic codebook mode; and

the transceiver unit is further configured to configure thesemi-persistent codebook mode for the terminal device by usingsignaling.

With reference to the fourth aspect, in some implementations of thefourth aspect, the first preset value is greater than or equal to 1, andwhen the first preset value is greater than 1, first downlinkinformation whose number of pieces is equal to the first preset valuecarries same transport block information.

With reference to the fourth aspect, in some implementations of thefourth aspect, the first downlink information whose number of pieces isequal to the first preset value is scheduled by one downlink controlchannel.

With reference to the fourth aspect, in some implementations of thefourth aspect, the first preset value is less than or equal to a thirdpreset value, and the third preset value is determined based on adownlink aggregation parameter configured by using higher layersignaling.

According to a fifth aspect, a communication device for transmittingfeedback information is provided. The device includes a memory and aprocessor, where the memory is configured to store a computer program,and the processor is configured to invoke and run the computer programin the memory, so that the communication device performs either themethod in the first aspect and the implementations of the first aspector the method in the second aspect and the implementations of the secondaspect.

According to a sixth aspect, a communication system is provided, wherethe system includes the communication device in the third aspect or anypossible implementation of the third aspect and the communication devicein the fourth aspect or any possible implementation of the fourthaspect.

According to a seventh aspect, a chip system is provided, including amemory and a processor, where the memory is configured to store acomputer program, and the processor is configured to invoke and run thecomputer program in the memory, so that a communication device providedwith the chip system performs either the method in the first aspect andthe implementations of the first aspect or the method in the secondaspect and the implementations of the second aspect.

According to an eighth aspect, a computer program product is provided,where the computer program product includes computer program code, andwhen the computer program code is run by a communication unit and aprocessing unit or a transceiver and a processor that are of acommunication device (for example, a terminal device or a networkdevice), the communication device is enabled to perform either themethod in the first aspect and the implementations of the first aspector the method in the second aspect and the implementations of the secondaspect.

According to a ninth aspect, a computer-readable storage medium isprovided, where the computer-readable storage medium stores a program,and the program enables a communication device (for example, a terminaldevice or a network device) to perform either the method in the firstaspect and the implementations of the first aspect or the method in thesecond aspect and the implementations of the second aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a communication system;

FIG. 2 is a schematic diagram of an association relationship in an LTEsystem based on a semi-persistent codebook (a single time divisionduplex (TDD) carrier is used as an example) according to an embodimentof this application;

FIG. 3 is a schematic diagram of an association relationship in a 5Gcommunication system (a single TDD carrier is used as an example)according to an embodiment of this application;

FIG. 4 is an interaction flowchart of sending feedback information by aterminal device according to an embodiment of this application;

FIG. 5 is a schematic diagram of scheduling a plurality of PDSCHs byusing one piece of downlink control information (DCI) according to anembodiment of this application;

FIG. 6 is a schematic diagram of a feedback information fallback modeaccording to an embodiment of this application;

FIG. 7 is a schematic diagram of a feedback information fallback modeaccording to an embodiment of this application;

FIG. 8 is a schematic diagram of a communication device according to anembodiment of this application;

FIG. 9 is a schematic diagram of a communication device according to anembodiment of this application;

FIG. 10 is a schematic block diagram of a communication device accordingto another embodiment of this application; and

FIG. 11 is a schematic block diagram of a communication device accordingto another embodiment of this application.

DETAILED DESCRIPTION

The following describes technical solutions provided by embodiments ofthis application with reference to accompanying drawings.

The technical solutions in the embodiments of this application may beapplied to various communication systems, such as global systems formobile communications (GSM), code division multiple access (CDMA)systems, wideband code division multiple access (WCDMA) systems, generalpacket radio service (GPRS) systems, long term evolution (LTE) systems,LTE frequency division duplex (FDD) systems, LTE time division duplex(TDD) systems, universal mobile telecommunications service (UMTS)systems, worldwide interoperability for microwave access (WiMAX)communications systems, future 5th Generation (5G) systems, or new radio(NR) systems.

A terminal device in the embodiments of this application may correspondto various devices in technical literature, such as user equipment, anaccess terminal, a subscriber unit, a subscriber station, a mobilestation, a mobile console, a remote station, a remote terminal, a mobiledevice, a user terminal, a terminal, a wireless communication device, auser agent, or a user communication device. The terminal device mayalternatively be referred to as a cellular phone, a cordless phone, asession initiation protocol (SIP) phone, a wireless local loop (WLL)station, a personal digital assistant (PDA), a handheld device, acomputing device having a wireless communication function, a processingdevice connected to a wireless modem, a vehicle-mounted device, aterminal device in a future 5G network, a terminal device in a futureevolved public land mobile network (PLMN), or the like. This is notlimited in the embodiments of this application.

Further, in the embodiments of this application, the terminal device mayalternatively be a wearable device. The wearable device may also bereferred to as a wearable intelligent device, and is a general term forwearable devices, for example, glasses, gloves, watches, clothing, andshoes, that are developed through intelligent design for daily wearablesby using a wearable technology. The wearable device is a portable devicethat is worn directly on the body or integrated into a user's clothingor accessory. A wearable device is not only a hardware device, but alsoimplements powerful functions through software support, data exchange,and cloud-based interaction. In a broad sense, a wearable intelligentdevice includes a device that provides a complete function, has a largesize, and can implement all or some functions without relying on asmartphone, for example, a smartwatch or smart glasses; and includes adevice that focuses only on a specific type of application function andthat needs to be used in combination with another device such as asmartphone, for example, various smart bands and smart jewelry used forvital sign monitoring.

In addition, in the embodiments of this application, the terminal devicemay alternatively be a terminal device in an Internet of Things (IoT)system. IoT is an important part of future development of informationtechnologies, and a main technical feature of IoT is to connect anobject to a network by using communication technologies, therebyimplementing an intelligent network for interconnection between a personand a machine or between one object and another.

In the embodiments of this application, the IoT technology can implementmassive connections, in-depth coverage, and power saving for terminalsby using, for example, a narrow band (NB) technology. For example, an NBresource includes only one resource block (RB). In other words, abandwidth of the NB is only 180 KB. To implement massive connections,terminals need to perform discrete access. With communication methodsaccording to the embodiments of this application, a congestion problemthat occurs when massive terminals access a network based on NB by usingthe IoT technology can be effectively resolved.

In the embodiments of this application, a network device may be anaccess network device or a core network device.

The access network device may be a device configured to communicate witha terminal device. The access network device may be an access point (AP)in a wireless local area network (WLAN), a base transceiver station(BTS) in GSM or CDMA, a NodeB (NB) in wideband code division multipleaccess (WCDMA), a gNB in a new radio (NR) system, an evolved NodeB (eNBor eNodeB) in LTE, a relay node, an access point, a vehicle-mounteddevice, a wearable device, an access network device in a future 5Gnetwork, an access network device in a future evolved PLMN network, orthe like.

The access network device provides a service for a cell, and theterminal device communicates with the access network device by using atransmission resource (for example, a frequency domain resource or aspectrum resource) used by the cell. The cell may be a cellcorresponding to the access network device (for example, a basestation). The cell may belong to a macro base station or a base stationcorresponding to a small cell. The small cell herein may include a metrocell, a micro cell, a pico cell, a femto cell, or the like. These smallcells feature small coverages and low transmission power, and aresuitable for providing high-rate data transmission services.

In addition, on a carrier in an LTE system or a 5G system, a pluralityof cells may work at one frequency. In some special scenarios, it mayalso be considered that a concept of a carrier is equivalent to aconcept of a cell. For example, in a carrier aggregation (CA) scenario,when a secondary component carrier is configured for a terminal device,a configuration carries both a carrier index of the secondary componentcarrier and a cell identity (Cell ID) of a secondary serving cellworking on the secondary component carrier. In this case, it may beconsidered that the concept of carrier is equivalent to the concept ofcell. For example, that a terminal device accessing a carrier isequivalent to the terminal device accessing a cell.

The core network device may be connected to a plurality of accessnetwork devices, configured to control the access network devices, andcan distribute data received from a network side (for example, theInternet) to the access network devices.

It should be understood that the foregoing listed functions and specificimplementations of the terminal device, the access network device, andthe core network device are merely examples, and this application is notlimited thereto.

FIG. 1 is a schematic diagram of a system 100 to which a communicationmethod provided in an embodiment of this application may be applied. Asshown in FIG. 1 , the system 100 includes a network device 102, and thenetwork device 102 may include one or more antennas, for example,antennas 104, 106, 108, 110, 112, and 114. In addition, the networkdevice 102 may additionally include a transmitter chain and a receiverchain. The transmitter chain and the receiver chain each may include aplurality of components related to signal transmission and reception(such as a processor, a modulator, a multiplexer, a demodulator, ademultiplexer, or an antenna).

The network device 102 may communicate with a plurality of terminaldevices (for example, a terminal device 116 and a terminal device 122).However, it can be understood that the network device 102 maycommunicate with any number of terminal devices similar to the terminaldevice 116 or the terminal device 122. The terminal devices 116 and 122may be, for example, cellular phones, smartphones, portable computers,handheld communication devices, handheld computing devices, satelliteradio communication devices, global positioning systems, PDAs, and/orany other appropriate devices that are configured to performcommunication in the system 100.

As shown in FIG. 1 , the terminal device 116 communicates with theantennas 112 and 114. The antennas 112 and 114 send information to theterminal device 116 through a forward link (which may also be referredto as a downlink) 118, and receive information from the terminal device116 through a reverse link (which may also be referred to as an uplink)120. In addition, the terminal device 122 communicates with the antennas104 and 106. The antennas 104 and 106 send information to the terminaldevice 122 through a forward link 124, and receive information from theterminal device 122 through a reverse link 126.

For example, in a frequency division duplex (FDD) system, a frequencyband used on the forward link 118 may be different from that used on thereverse link 120, and a frequency band used on the forward link 124 maybe different from that used on the reverse link 126.

For another example, in a time division duplex (TDD) system or a fullduplex system, a frequency band used on the forward link 118 may be thesame as that used on the reverse link 120, and a frequency band used onthe forward link 124 may be the same as that used on the reverse link126.

A coverage area of each antenna (or an antenna group including aplurality of antennas) and/or a transmission area that are/is designedfor communication are/is referred to as a sector of the network device102. For example, an antenna group may be designed to communicate with aterminal device in a sector, namely, a coverage area, of the networkdevice 102. A network device can send signals to all terminal devices ina sector corresponding to the network device by using a single antennaor through multi-antenna transmit diversity. In a process in which thenetwork device 102 communicates with the terminal devices 116 and 122through the forward links 118 and 124 respectively, transmit antennas ofthe network device 102 can increase signal-to-noise ratios of theforward links 118 and 124 through beamforming. In addition, comparedwith a manner in which a network device sends, by using a single antennaor through multi-antenna transmit diversity, signals to all terminaldevices served by the network device, when the network device 102 sends,through beamforming, signals to the terminal devices 116 and 122randomly scattered in a related coverage area, a mobile device in aneighboring cell suffers from less interference.

Within a given time period, the network device 102, the terminal device116, or the terminal device 122 may be a wireless transmission deviceand/or a wireless receiving device. When sending data, the wirelesstransmission device may encode the data for transmission. Specifically,the wireless transmission device may obtain (for example, by generating,by receiving from another communication device, or by storing in amemory) a specific number of data bits to be transmitted to the wirelessreceiving device through a channel. Such data bits may be included in atransport block (or a plurality of transport blocks), and the transportblock may be segmented into a plurality of code blocks.

In addition, the system 100 may be a PLMN network, a device-to-device(D2D) network, a machine-to-machine (M2M) network, an IoT network, oranother network. FIG. 1 is merely a simplified schematic diagram. Thenetwork may further include other network device that are not shown inFIG. 1 .

The network device may be a network device in a current network, anetwork device in a future evolved PLMN network, or the like. This isnot limited in the embodiments of this application.

The following describes in detail a to-be-transmitted object (that is,feedback information) in the embodiments of this application.

In the embodiments of this application, a feedback technology may beused for downlink data transmission. By way of example but notlimitation, the feedback technology may include, for example, a hybridautomatic repeat request (HARQ) technology.

The HARQ technology is a technology formed by combining forward errorcorrection (FEC) coding with an automatic repeat request (ARQ)technology.

For example, in the HARQ technology, after receiving data from atransmit end, a receive end may determine whether the data is correctlydecoded. If the data is not correctly decoded, the receive end may feedback NACK information to the transmit end, so that the transmit end candetermine, based on the NACK information, that the receive end has notcorrectly received the data, and thereby may perform retransmission. Ifthe data is correctly decoded, the receive end may feed back ACKinformation to the transmit end, so that the transmit end can determine,based on the ACK information, that the receive end has correctlyreceived the data, and thereby can determine that data transmission iscompleted.

In other words, in the embodiments of this application, the receive endmay send the ACK information to the transmit end when decoding issuccessfully, and may send the NACK information to the transmit end whendecoding is unsuccessful.

By way of example but not limitation, in the embodiments of thisapplication, uplink control information may include ACK information orNACK information in the HARQ technology.

In an LTE system, a downlink slot and an uplink slot are respectivelybased on orthogonal frequency division multiple access (OFDMA) andsingle-carrier frequency division multiple access (SC-FDMA). Atime-frequency resource is divided into OFDM or SC-FDMA symbols(referred to as time domain symbols below) in a time domain dimensionand subcarriers in a frequency domain dimension. A smallest resourcegranularity is referred to as a resource element (RE), and represents atime-frequency grid point including a time domain symbol in time domainand a subcarrier in frequency domain.

Service transmission in the LTE system is based on scheduling by a basestation. A basic time unit for scheduling is one subframe, and onesubframe includes a plurality of time domain symbols. A specificscheduling procedure is that the base station sends a control channel,for example, a physical downlink control channel (PDCCH) or an enhancedphysical downlink control channel (EPDCCH). The control channel maycarry scheduling information of a physical downlink shared channel(PDSCH) or a physical uplink shared channel (PUSCH), and the schedulinginformation includes, for example, control information such as resourceallocation information and a modulation and coding scheme (MCS). Aterminal device detects a control channel in a subframe, and performsdownlink data channel receiving or uplink data channel sending based onscheduling information carried on the detected control channel. In theembodiments of this application, a PDCCH is used as an example fordescribing a downlink control channel, a PDSCH is used as an example fordescribing a downlink data channel, a physical uplink control channel(PUCCH) is used as an example for describing an uplink control channel,an ACK/NACK is used as an example for describing feedback information, acarrier is used as an example for describing a frequency domain unit, asubframe is used as an example for describing a time unit in the LTEsystem, a slot is used as an example for describing a time unit in a 5Gsystem, and a base station is used as an example for describing anetwork device. This application is not limited thereto.

The LTE system supports two duplex modes: FDD and TDD. In an FDD system,a downlink subframe and an uplink subframe are used for transmission ondifferent carriers. In a TDD system, an uplink subframe and a downlinksubframe are used for transmission at different times on one carrier. Ina frame structure in TDD, a special subframe may be used as a downlinksubframe. The special subframe can carry downlink data but cannot carryuplink data.

A HARQ mechanism is used for the LTE system, and downlink transmissionis used as an example. After the terminal device receives the PDSCH, ifthe PDSCH is correctly received, the terminal device feeds back an ACKon the PUCCH. If the PDSCH is not correctly received, the terminaldevice feeds back an NACK on the PUCCH. In FDD, for example, afterreceiving the PDSCH in a subframe n-4, the terminal device feeds back anACK/NACK in a subframe n. In TDD, for example, a timing relationshipbetween PDSCH reception and corresponding ACK/NACK feedback is shown inTable 1. A numbered subframe is an uplink subframe n used for ACK/NACKfeedback, and an identification number indicates that an ACK/NACKcorresponding to a PDSCH in a downlink subframe set corresponding to n-k(k belongs to K) downlink subframes needs to be fed back in the uplinksubframe n.

For example, as shown in Table 1 below, K={7, 6} corresponding to asubframe n=2 in an uplink/downlink configuration 1 indicates that thesubframe n=2 is used to feed back ACKs/NACKs corresponding to PDSCHs intwo downlink subframes corresponding to n-7 and n-6. Specifically, n-7indicates a downlink subframe 5, and n-6 indicates a downlink subframe6.

TABLE 1 Uplink/Downlink Subframe number n configuration 0 1 2 3 4 5 6 78 9 0 — — 6 — 4 — — 6 — 4 1 — — 7, 6 4 — — — 7, 6 4 — 2 — — 8, 7, 4, 6 —— — — 8, 7, 4, 6 — — 3 — — 7, 6, 11 6, 5 5, 4 — — — — — 4 — — 12, 8, 7,11 6, 5, 4, 7 — — — — — — 5 — — 13, 12, 9, 8, 7, 5, 4, 11, 6 — — — — — —— 6 — — 7 7 5 — — 7 7 —

The LTE system also supports a carrier aggregation (CA) technology. Tobe specific, a base station configures a plurality of carriers for oneterminal device, to increase a data rate of the terminal device. DuringCA, the plurality of carriers sent by the base station are synchronizedin time. The terminal device can separately detect a PDCCH forscheduling each carrier and a corresponding PDSCH, where a specificdetection procedure for each carrier is similar to the foregoing case ofa single carrier.

The LTE system also supports FDD CA, TDD CA, and FDD+TDD CA. In a CAmode, there is one primary component carrier and at least one secondarycomponent carrier. In a typical configuration, a PUCCH carrying anACK/NACK is sent only on a primary component carrier of the terminaldevice. In a PUCCH sending mode in the CA mode, a PUCCH format 3 mode isusually used. In the PUCCH format 3 mode, a DFT-S-OFDM sending structureis used. The structure can support transmission of a maximum of 20ACK/NACK bits and support TDD CA of five carriers.

A mainstream deployment, a TDD uplink/downlink configuration 2, in acurrent network is used as an example. An uplink subframe 2corresponding to one carrier may support feedback of four ACK/NACK bits,and TDD CA of five carriers that corresponds to the TDD uplink/downlinkconfiguration 2 corresponds to 20 ACK/NACK bits. The 20 bits form anACK/NACK codebook, that is, a bitstream of original ACK/NACK bits beforecoding that are arranged in an order.

It should be understood that the foregoing listed content included infeedback information is merely used as an example for description, andthis application is not limited thereto.

An uplink ACK/NACK codebook configuration in the LTE system includes asemi-persistent codebook configuration and a dynamic codebookconfiguration. In the dynamic codebook configuration, a codebook isdetermined based on the number of PDSCHs scheduled in real time.

In the semi-persistent codebook configuration, a codebook is determinedbased on the number of downlink subframes in a semi-persistent downlinksubframe set.

For example, an ACK/NACK codebook includes feedback informationcorresponding to all downlink subframes in the semi-persistent downlinksubframe set. The downlink subframes include a downlink subframe for anactually scheduled PDSCH or a downlink subframe for semi-persistentscheduling (SPS) release indication, and also include an unscheduleddownlink subframe. An NACK is set in a position of in the codebookcorresponding to an unscheduled downlink subframe or a downlink subframewhose scheduling signaling is not received by a terminal device.

FIG. 2 is a schematic diagram of an association relationship in an LTEsystem (a single TDD carrier is used as an example) according to anembodiment of this application. Specifically, FIG. 2 is a schematicdiagram of a first association relationship based on a semi-persistentcodebook configuration in the LTE system.

In the semi-persistent codebook configuration, a subframe in which aPUCCH carrying an ACK/NACK codebook exists corresponds to asemi-persistent downlink subframe set.

For example, when five TDD carriers are configured for a terminal devicefor carrier aggregation (other scenarios may be considered as aparticular case of this scenario), a time set may include a plurality ofsubframes corresponding to these TDD carriers configured for theterminal device.

It is assumed that uplink/downlink subframe configurations of the TDDcarriers are identical. For example, an uplink subframe 2, in which aPUCCH carrying an ACK/NACK codebook exists, corresponds to a downlinksubframe set {4, 5, 6, 8} in each of these TDD carriers.

As shown in FIG. 2 (one carrier is used as an example herein), theACK/NACK codebook includes feedback information corresponding to fourdownlink subframes in each of the 5 TDD carriers. In other words, a sizeof the codebook, that is, the number of bits of the ACK/NACK codebook,is 20. Herein, it is assumed that one downlink subframe corresponds toone ACK/NACK bit.

There is an association relationship between the uplink subframe 2 andthe downlink subframes {4, 5, 6, 8} corresponding to each carrier. Inthe LTE system, the association relationship may be preconfiguredaccording to a standard. That is, the association relationship does notneed to be notified to the terminal device by using signaling.

In other words, after obtaining a TDD uplink/downlink configuration, theterminal device obtains an association relationship corresponding to theuplink/downlink configuration, thereby obtaining a timing relationshipbetween a downlink subframe carrying a PDSCH and a corresponding uplinksubframe for feeding back an ACK/NACK.

For example, the timing relationship may be the timing relationshipbetween PDSCH reception and corresponding ACK/NACK feedback shown inTable 1.

As shown in FIG. 2 , in the downlink subframes {4, 5, 6, 8}, thedownlink subframes {6, 8} may be scheduled downlink subframes, and thedownlink subframes {4, 5} may be unscheduled downlink subframes. Theterminal device may determine whether data in the downlink subframes {6,8} is correctly decoded, and send ACK/NACK information in the uplinksubframe 2. Because the downlink subframes {4, 5} are unscheduled, forthe downlink subframes, NACKs need to be sent in the uplink subframe 2.

Therefore, in the current LTE system, for feedback information in thesemi-persistent codebook configuration, a codebook of the feedbackinformation is determined based on the number of downlink subframes inthe semi-persistent downlink subframe set.

The LTE system further supports a fallback mechanism in thesemi-persistent codebook configuration.

For example, if a PUCCH format 3, format 4, or format 5 PUCCH sendingmode (an ACK/NACK of more than two bits can be carried in each of PUCCHsof these formats) is configured for the terminal device:

in a codebook and resource fallback mode: if the terminal devicereceives only a primary PDCCH for scheduling a PDSCH on a primarycomponent carrier, and a DAI field on the primary PDCCH is indicated as‘1’, the terminal device uses a PUCCH format 1a/1b to feed back 1-bit(for a single codebook) or 2-bit (for two codebooks) ACK/NACKinformation; or

in a non-fallback mode: if the terminal device receives a primary PDCCHfor scheduling a PDSCH on a primary component carrier, and a valueindicated by a DAI field on the primary PDCCH is greater than ‘1’, orthe terminal device receives a secondary PDCCH for scheduling a PDSCH ona secondary component carrier, the terminal device uses a PUCCH format 3to feed back an ACK/NACK. A channel resource of the PUCCH format 3 isexplicitly indicated by a 2-bit field in the primary PDCCH, includingthe DAI value greater than 1, or a 2-bit field on the secondary PDCCH.

In this case, the ACK/NACK codebook includes feedback informationcorresponding to all downlink subframes in the semi-persistent downlinksubframe set. The downlink subframes include a downlink subframe for anactually scheduled PDSCH or a downlink subframe for SPS releaseindication, and also include an unscheduled downlink subframe. A NACK isset in a position of the codebook corresponding to an unscheduleddownlink subframe or a downlink subframe whose scheduling signaling isnot received by the terminal device.

In a special fallback mode (an SPS PDSCH is considered): if the terminaldevice receives only a primary PDCCH for scheduling a PDSCH on a primarycomponent carrier and an SPS PDSCH, and a DAI field on the primary PDCCHis indicated as ‘1’, the SPS PDSCH is not dynamically scheduled througha PDCCH in most cases, and no field for indicating a PUCCH format 3resource exists on the primary PDCCH.

Therefore, in this case, it is not possible to roll back to the PUCCHformat 1a/1b, and the PUCCH format 3 resource cannot be used to carry anon-fallback codebook. A solution used in the LTE system is the specialfallback mode. Specifically, channel selection is performed between adynamic PUCCH format 1a/1b resource determined through the primary PDCCHand a semi-persistent PUCCH format 1a/1b resource corresponding to theSPS PDSCH.

A 5G system also supports the foregoing semi-persistent codebookconfiguration, the fallback codebook, and the fallback schedulingmechanism. However, different from the LTE system, there are a firstassociation relationship and a second association relationship in the 5Gsystem. The following describes the fallback codebook and the fallbackscheduling mechanism in the 5G system based on the first associationrelationship and the second association relationship in the 5G system.

The first association relationship and the second associationrelationship in the 5G system are described first.

FIG. 3 is a schematic diagram of an association relationship in a 5Gsystem according to an embodiment of this application. As shown in FIG.3 , there are two association relationships in a semi-persistentcodebook configuration in the 5G system.

It should be understood that this embodiment of this application ismainly about the semi-persistent codebook configuration and thefollowing descriptions are mainly based on the semi-persistent codebookconfiguration.

A first association relationship is similar to the foregoing associationrelationship in the LTE system, but supports a more flexibleconfiguration.

For example, the first association relationship may be preconfigured ornotified to a terminal device by using RRC dedicated signaling.

In other words, for fallback PDCCH scheduling, the first associationrelationship may be preconfigured. For non-fallback PDCCH scheduling,the first association relationship may be notified to the terminaldevice by using RRC dedicated signaling.

If the terminal device needs to detect the two types of PDCCHs, thefirst association relationship may be a union set of the preconfiguredassociation relationship and the association relationship notified byusing signaling.

For example, a semi-persistent codebook that needs to be fed back in anuplink slot n may correspond to downlink slots {n-1, n-2, n-3, n-4, n-5,n-6, n-7, n-8}, where n-1 to n-8 may be preconfigured, or notified tothe terminal device by using RRC dedicated signaling.

In addition, the first association relationship may be related to aPDCCH detection slot.

For example, the first association relationship may be an intersectionset between the union set of the preconfigured association relationshipand the association relationship notified by using RRC signaling and thePDCCH detection slot.

For example, a cycle of the PDCCH detection slot is two slots, that is,a PDCCH needs to be detected in slots {n-1, n-3, n-5, n-7}. In thiscase, the first association relationship may be an intersection setbetween {n-1, n-2, n-3, n-4, n-5, n-6, n-7, n-8} and {n-1, n-3, n-5,n-7}, that is, {n-1, n-3, n-5, n-7}.

However, a configuration of the PDCCH detection slot may alternativelybe preconfigured, or notified to the terminal device by using RRCdedicated signaling. Therefore, the first association relationship maybe preconfigured, or notified to the terminal device by using RRCdedicated signaling.

A second association relationship is determined based on timingindication information on a PDCCH. In other words, the secondassociation relationship is indicated to the terminal device by usingthe timing indication information on the PDCCH.

For example, the PDCCH includes 3-bit timing indication information,such as timing indication on downlink control information (DCI). Thetiming indication information is used to indicate a timing relationshipbetween a slot in which a PDSCH scheduled through the PDCCH is locatedand a slot in which an ACK/NACK is located.

For example, when the first association relationship is {n-1, n-2, n-3,n-4, n-5, n-6, n-7, n-8}, timing indication information on a PDCCH maybe one of the eight values in the first association relationship.

As shown in FIG. 3 , for an uplink slot i, slot sets corresponding tothe first association relationship and the second associationrelationship may be the same, that is, each of the slot set includesdownlink slots 1 to 8. For an uplink slot j, a slot set corresponding tothe first association relationship is still downlink slots 1 to 8, but aslot set corresponding to the second association relationship mayinclude only downlink slots 1 and 2. In other words, the slot setcorresponding to the second association relationship may be a subset ofthe slot set corresponding to the first association relationship.

In this embodiment of this application, different from the LTE system,there are the first association relationship and the second associationrelationship in the 5G system.

With reference to specific examples, the following describes in detailembodiments of a fallback codebook and a fallback scheduling mechanismbased on the first association relationship and the second associationrelationship in the 5G system.

It should be noted that the description is merely intended to helpunderstanding of the embodiments of this application, but are notintended to limit the scope of the embodiments of this application.

It should be understood that in the embodiments of this application,first downlink information, second downlink information, a firstcodebook, a second codebook, “first”, “second”, and the like are merelyused to indicate different objects, and do not mean that any otherlimitations are imposed on the indicated objects.

FIG. 4 is an interaction flowchart of sending feedback information by aterminal device according to an embodiment of this application.

The terminal device in FIG. 4 may be any terminal device in FIG. 1 , anda network device in FIG. 4 may be the network device in FIG. 1 . This isnot limited in this application.

It should be noted that in this embodiment of this application, downlinkinformation may be a PDSCH. This is not limited in this application.

S410: The terminal device receives at least one piece of downlinkinformation in at least one first time unit in a time unit set, wherethe time unit set is a set of at least one first time unit correspondingto at least one frequency domain unit configured for the terminaldevice.

In other words, the network device sends at least one piece of downlinkinformation to the terminal device in at least one first time unit in atime unit set, where the time unit set is a set of at least one firsttime unit corresponding to at least one frequency domain unit configuredfor the terminal device.

It should be understood that the time unit set may be a set of at leastone first time unit in different frequency domain units. The first timeunit may be a downlink time unit or a flexible time unit, and is usedfor receiving downlink information. In the first time unit, one piece ofdownlink information or a plurality of pieces of downlink informationmay be received. This is not limited in this application.

Optionally, a time unit may be at least one of a slot, a mini-slot, anda subframe. For example, in this embodiment of this application, a slotmay be used as an example for description.

Optionally, a frequency domain unit may be a carrier or a carrier BWP.For example, in this embodiment of this application, a carrier may beused as an example for description.

S420: The terminal device determines a second time unit, where thesecond time unit is used to carry feedback information corresponding tothe at least one piece of downlink information, and there is a firstassociation relationship between the time unit set and the second timeunit.

Optionally, the second time unit may be an uplink time unit or aflexible time unit. For example, in this embodiment of this application,an uplink slot may be used as an example for description.

Optionally, the first association relationship may be preconfigured, ornotified to the terminal device by using RRC dedicated signaling.Generally, for fallback PDCCH scheduling, the first associationrelationship may be preconfigured. For non-fallback PDCCH scheduling,the first association relationship may be notified to the terminaldevice by using RRC dedicated signaling.

S430: The terminal device determines a first codebook, where when firstdownlink information in a subset of the time unit set (referred to astime unit subset) meets a preset condition, the first codebook includesfeedback information corresponding to the first downlink information,the first codebook does not include feedback information correspondingto a specific time unit in the time unit subset, the specific time unitis at least one first time unit in the time unit set other than a firsttime unit in which the first downlink information is located, the presetcondition includes a first condition, the first condition is that thenumber of pieces of first downlink information is equal to a firstpreset value, the time unit subset is a subset of the time unit set, andthere is a second association relationship between the time unit subsetand the second time unit.

In other words, when the first downlink information in the time unitsubset meets the condition that the number of pieces of the firstdownlink information is equal to the first preset value, the firstcodebook may include only the feedback information corresponding to thefirst downlink information.

Specifically, this solution may also be applied to the following case: Aplurality of PDSCHs that do not overlap in time domain may be scheduledfor one terminal device in one first time unit corresponding to onefrequency domain unit. For example, one first time unit includes 14 timedomain symbols. It is preconfigured that a time domain location in thefirst time unit includes the 1^(st) to the 7^(th) time domain symbolsand the 8^(th) to the 14^(th) time domain symbols. These two groups oftime domain locations do not overlap in time domain, and in a normalnon-fallback semi-persistent codebook, the first time unit correspondsto feedback of a 2-bit ACK/NACK.

The pre-configuration is performed by using RRC signaling. Specifically,a time domain location to be actually scheduled is indicated by a timedomain resource assignment indicator field on the PDCCH. For example,one bit on the PDCCH may be used to specifically indicate one of theforegoing two groups of time domain locations.

In this scenario, the first codebook includes the feedback informationcorresponding to the first downlink information. The first codebook doesnot include the feedback information corresponding to the specific timeunit in the time unit subset, and the first codebook does not includefeedback information corresponding to a time domain location, in thefirst time unit in which the PDSCH is located, other than a time domainlocation in which the PDSCH is located. In other words, in this case,the first codebook includes only the first downlink information, thatis, feedback information corresponding to the PDSCH.

Alternatively, in the foregoing scenario, the different time domainlocations may be considered as different first time units. For example,the 1^(st) to the 7^(th) time domain symbols and the 8^(th) to the14^(th) time domain symbols are respectively considered as two firsttime units. In this case, the first codebook includes the feedbackinformation corresponding to the first downlink information, and thefirst codebook does not include the feedback information correspondingto the specific time unit in the time unit subset.

When the number of pieces of the first downlink information in the timeunit subset does not meet the first condition, the first codebookincludes feedback information corresponding to all the first time unitsin the time unit set.

For example, the first preset value may be 1, and a downlink slot setincludes a downlink slot 1 to a downlink slot 8, that is, the time unitset includes the downlink slots 1 to 8. A downlink slot subsetcorresponding to an uplink slot includes the downlink slot 1 and thedownlink slot 2, that is, the time unit subset includes the downlinkslot 1 and the downlink slot 2.

When the number of PDSCHs received in the downlink slot 1 and thedownlink slot 2 is 1, the first condition included in the presetcondition is met. For example, only a PDSCH in the downlink slot 1 isreceived. In this case, an ACK/NACK codebook may include only anACK/NACK corresponding to the PDSCH in the downlink slot 1, and does notinclude an ACK/NACK corresponding to another downlink slot in thedownlink slot set, that is, the downlink slots 1 to 8.

When the number of PDSCHs received in the downlink slot 1 and thedownlink slot 2 is not 1, the first condition included in the presetcondition is not met. For example, a PDSCH in the downlink slot 1 and aPDSCH in the downlink slot 2 are received. In this case, an ACK/NACKcodebook includes ACK/NACKs corresponding to PDSCHs in the downlink slotset, that is, the downlink slots 1 to 8. In other words, no codebookfallback is performed, and a normal semi-persistent codebook is usedinstead. This is not limited in this application.

For another example, the first preset value may be 2. In this case, itis assumed that two dynamically scheduled PDSCHs may be received in onedownlink slot corresponding to one carrier. For example, a plurality oftransmission points or base stations each send one dynamically scheduledPDSCH to the terminal device in one downlink slot corresponding to onecarrier. The first condition is that when the number of PDSCHs receivedin one of the downlink slot 1 and the downlink slot 2 is 2, the firstcondition included in the preset condition is not met. For example, onlytwo PDSCHs in the downlink slot 1 are received. In this case, anACK/NACK codebook may include only ACKs/NACKs corresponding to the twoPDSCHs in the downlink slot 1, and does not include an ACK/NACKcorresponding to another downlink slot in the downlink slot set, thatis, the downlink slots 1 to 8. When the number of PDSCHs received in thedownlink slot 1 and the downlink slot 2 does not meet the firstcondition included in the preset condition, for example, PDSCHs in thedownlink slot 1 and PDSCHs in the downlink slot 2 are received, theACK/NACK codebook includes ACK/NACKs corresponding to PDSCHs in thedownlink slot set, that is, the downlink slots 1 to 8. In other words,no codebook fallback is performed, and a normal semi-persistent codebookis used instead. It should be understood that this is not limited inthis application.

Optionally, the technical solution in this embodiment of thisapplication is applicable to a scenario in which one piece of DCI isused for scheduling a plurality of PDSCHs. As shown in FIG. 5 , for anuplink slot i, slot sets corresponding to a first associationrelationship and a second association relationship may be the same, thatis, each of the slot sets includes downlink slots 1 to 8. For an uplinkslot j, a slot set corresponding to the first association relationshipis still downlink slots 1 to 8, but a slot set corresponding to thesecond association relationship may include only downlink slots 1 and 2,that is, a time unit subset includes the downlink slot 1 and thedownlink slot 2. In addition, a PDSCH in the downlink slot 1 and a PDSCHin the downlink slot 2 are scheduled by using one piece of DCI. In otherwords, this is the scenario in which one piece of DCI is used forscheduling a plurality of PDSCHs.

The first preset value is X, where X may be a positive integer greaterthan or equal to 1. For example, X=1, 2, 3, 4, 5, 6, 7, 8. The firsttime unit may be a time unit corresponding to a symbol in which the lastpiece of first downlink information in a plurality of pieces of firstdownlink information is located, or may be a time unit corresponding toa symbol in which the first piece of first downlink information in theplurality of pieces of first downlink information is located. Forexample, four PDSCHs are in a downlink slot 1 to a downlink slot 4. Afirst time unit corresponding to the four PDSCHs may be the downlinkslot 4, or may be the downlink slot 1.

For example, in this embodiment of this application, the first presetvalue may be 4. It is assumed that four PDSCHs may be received in atleast one downlink slot corresponding to one carrier, and the fourPDSCHs are used to carry same transport block information. The fourPDSCHs are scheduled by using one piece of DCI when the time unit subsetmeets the first condition included in the preset condition, that is,when the number of pieces of the first downlink information in the timeunit subset is equal to the first preset value, the terminal deviceperforms codebook fallback.

For example, the downlink slot set includes the downlink slot 1 to thedownlink slot 8, and the downlink slot subset corresponding to theuplink slot includes the downlink slot 1 and the downlink slot 2, thatis, the time unit subset includes the downlink slot 1 and the downlinkslot 2. If the number of PDSCHs received only in the downlink slot 2 is4, the ACK/NACK codebook may include only an ACK/NACK corresponding tothe four PDSCHs in the downlink slot 2, and does not include an ACK/NACKcorresponding to another downlink slot in slots 1 to 8 in the downlinkslot set. If the number of PDSCHs received in the downlink slot 1 is 4,and the number of PDSCHs received in the downlink slot 2 is 4, theACK/NACK codebook includes ACKs/NACKs corresponding to PDSCHs in thedownlink slot 1 to 8 in the downlink slot set. In other words, nocodebook fallback is performed, and a normal semi-persistent codebook isused instead.

It should be noted that in this embodiment of this application, the timeunit subset meets the first condition included in the preset condition.That is, the number of pieces of the first downlink information in thetime unit subset is equal to the first preset value. The number ofpieces of first downlink information in only one time unit in the timeunit subset may be equal to the first preset value, or the number ofpieces of first downlink information in only one time unit in the timeunit subset may be less than the first preset value.

For example, in this embodiment of this application, the first presetvalue may be 4. It is assumed that four PDSCHs may be received in atleast one downlink slot corresponding to one carrier, and the fourPDSCHs are used to carry same transport block information. The fourPDSCHs are scheduled by using one piece of DCI. In this case, when thefirst condition is that the number of PDSCHs received in at least onedownlink slot in the time unit subset is less than or equal to 4, thefirst condition included in the preset condition is met.

For example, only four PDSCHs in the downlink slot 1 are received. Inthis case, the ACK/NACK codebook may include only ACKs/NACKscorresponding to the four PDSCHs in the downlink slot 1, and does notinclude an ACK/NACK corresponding to another downlink slot in thedownlink slots 1 to 8 in the downlink slot set.

In this embodiment of this application, the number of pieces of thefirst downlink information in the time unit subset may be less than thefirst preset value. For example, only three PDSCHs in the downlink slot1 to the downlink slot 3 are received, and the three PDSCHs arescheduled by using one piece of DCI. In this case, the ACK/NACK codebookmay include only ACKs/NACKs corresponding to the three PDSCHs in thedownlink slot 1 to the downlink slot 3, and does not include an ACK/NACKcorresponding to another downlink slot in the downlink slots 1 to 8 inthe downlink slot set.

When the number of PDSCHs received in the time unit subset does not meetthe first condition included in the preset condition, the ACK/NACKcodebook includes ACKs/NACKs corresponding to PDSCHs in the downlinkslots 1 to 8 in the downlink slot set. In other words, no codebookfallback is performed, and a normal semi-persistent codebook is usedinstead.

For example, when five PDSCHs are received in at least one slot in thetime unit subset, the ACK/NACK codebook includes ACKs/NACKscorresponding to PDSCHs in the downlink slots 1 to 8 in the downlinkslot set. In other words, no codebook fallback is performed, and anormal semi-persistent codebook is used instead.

It should be understood that when a plurality of PDSCHs are received inat least one slot in the time unit subset, if the plurality of PDSCHsare not scheduled by using a same piece of DCI, no codebook fallback isperformed, and a normal semi-persistent codebook is used instead.

For example, when the first preset value may be 4, four PDSCHs arereceived in at least one slot in the time unit subset, and the fourPDSCHs are scheduled by using two pieces of DCI. In this case, theACK/NACK codebook includes an ACK/NACK corresponding to a PDSCH in thedownlink slots 1 to 8 in the downlink slot set. In other words, nocodebook fallback is performed, and a normal semi-persistent codebook isused instead. It should be understood that in this embodiment of thisapplication, 4 is merely an example for description, and does notconstitute a limitation on this embodiment of this application.

It should be noted that in this embodiment of this application, thefirst preset value needs to be less than or equal to a third presetvalue, where the third preset value is determined based on a downlinkaggregation parameter configured by using higher layer signaling from abase station, and the downlink aggregation parameter is the number ofretransmissions of information in the first downlink information. Thedownlink aggregation parameter may be the number of retransmissions ofinformation in the first downlink information in one slot, or thedownlink aggregation parameter may be the number of retransmissions ofinformation in the first downlink information in a plurality of slots.This is not limited in this application.

Optionally, the downlink aggregation parameter may be the number ofretransmissions of information in the first downlink information in oneslot. In this case, the first condition may be applied to one or moredownlink slots in the downlink slot set.

For example, the first preset value may be 2. It is assumed that twoPDSCHs may be received only in one downlink slot corresponding to onecarrier in the time unit subset (the downlink slot 1 and the downlinkslot 2), and the two PDSCHs are used to carry same transport blockinformation. The two PDSCHs are scheduled by using one piece of DCI. Inthis case, when the first condition may be that the number of PDSCHsreceived in one downlink slot in the time unit subset is less than orequal to 2, the first condition included in the preset condition is met.For example, only two PDSCHs in the downlink slot 1 are received. Inthis case, the ACK/NACK may include only ACKs/NACKs corresponding to thetwo PDSCHs in the downlink slot 1, and does not include an ACK/NACKcorresponding to another downlink slot in slots 1 to 8 in the downlinkslot set.

When the number of PDSCHs received in the time unit subset does not meetthe first condition included in the preset condition, for example, whenthree PDSCHs are received in a slot in the time unit subset, forexample, when three PDSCHs are received in the downlink slot 2, thenumber of PDSCHs, that is, 3, is greater than the first preset value.Therefore, the condition is not met. In this case, the ACK/NACK codebookincludes ACKs/NACKs corresponding to PDSCHs in the downlink slots 1 to 8in the downlink slot set. In other words, no codebook fallback isperformed, and a normal semi-persistent codebook is used instead.

A correspondence between the number of PDSCHs received in the time unitsubset and the downlink aggregation parameter does not meet the firstcondition included in the preset condition. For example, one PDSCH isreceived in the downlink slot 1 and one PDSCH is received in thedownlink slot 2. In this case, the ACK/NACK codebook includes ACKs/NACKscorresponding to PDSCHs in the downlink slots 1 to 8 in the downlinkslot set. In other words, no codebook fallback is performed, and anormal semi-persistent codebook is used instead. It should be understoodthat in this case, the two PDSCHs do not belong to one downlink slot.Therefore, it may be considered that a condition that the downlinkaggregation parameter is the number of retransmissions of information inthe first downlink information in one slot is not met. It should beunderstood that in this embodiment of this application, 2 is merely anexample for description, and does not constitute a limitation on thisembodiment of this application.

Optionally, the downlink aggregation parameter may be the number ofretransmissions of information in the first downlink information in aplurality of slots. In this case, the first condition is applied to aplurality of downlink slots in the downlink slot set.

For example, the first preset value may be 2. It is assumed that twoPDSCHs may be received in two downlink slots corresponding to onecarrier in the time unit subset (the downlink slot 1 and the downlinkslot 2), and the two PDSCHs are used to carry same transport blockinformation. The two PDSCHs are scheduled by using one piece of DCI. Inthis case, when the first condition is that the number of PDSCHsreceived in a plurality of downlink slots in the downlink slot set inthe time unit subset is less than or equal to 2, the first conditionincluded in the preset condition is met.

For example, one PDSCH is received in each of the downlink slot 1 andthe downlink slot 2. In this case, the ACK/NACK codebook may includeonly ACKs/NACKs corresponding to the two PDSCHs in the downlink slot 1and the downlink slot 2, and does not include an ACK/NACK correspondingto another downlink slot in the downlink slots 1 to 8 in the downlinkslot set.

When the number of PDSCHs received in the time unit subset does not meetthe first condition included in the preset condition, for example, whentwo PDSCHs are received in the downlink slot 1 and one PDSCH is receivedin the downlink slot 2, the ACK/NACK codebook includes ACKs/NACKscorresponding to PDSCHs in the downlink slots 1 to 8 in the downlinkslot set. In other words, no codebook fallback is performed, and anormal semi-persistent codebook is used instead. It should be understoodthat in this case, the number of PDSCHs, that is, 3, is greater than thefirst preset value. Therefore, it may be considered that the conditionis not met.

A correspondence between the number of received PDSCHs and the downlinkaggregation parameter does not meet the first condition included in thepreset condition. For example, only two PDSCHs are received in thedownlink slot 1. In this case, the ACK/NACK codebook includes ACKs/NACKscorresponding to PDSCHs in the downlink slots 1 to 8 in the downlinkslot set. In other words, no codebook fallback is performed, and anormal semi-persistent codebook is used instead. It should be noted thatin this case, the two PDSCHs belong to one downlink slot. Therefore, itmay be considered that a condition that the downlink aggregationparameter is the number of retransmissions of information in the firstdownlink information in a plurality of slots is not met. It should beunderstood that in this application, 2 is merely an example, and doesnot constitute a limitation.

It should be understood that when the first preset value is 8, eightPDSCHs are used to carry same transport block information. One bit maybe used to indicate whether the terminal device correctly decodes dataafter a receive end receives the transport block information carried onthe eight PDSCHs. Alternatively, eight bits may be used to indicatewhether the terminal device correctly decodes data after the receive endreceives transport block information carried on each of the eightPDSCHs. This is not limited in this embodiment of this application.

It should be noted that the first preset value is less than or equal toa third preset value, and the third preset value is determined based ona downlink aggregation parameter configured by using higher layersignaling. It may be understood that the downlink aggregation parametermay be the number of retransmissions of information in the firstdownlink information. When the third preset value is Y, X is less thanor equal to Y. Y may be a positive integer greater than or equal to 1.This is not limited in this application.

Optionally, in this case, the first condition includes that the numberof pieces of the first downlink information is less than or equal to thefirst preset value and not greater than the third preset value, the timeunit subset is a subset of the time unit set, and there is a secondassociation relationship between the time unit subset and the secondtime unit. Optionally, the first condition further includes that thedownlink aggregation parameter is greater than 1. Optionally, the firstpreset value is greater than 1.

Optionally, in this case, the first condition includes that the numberof pieces of the first downlink information is less than or equal to thefirst preset value, the time unit subset is a subset of the time unitset, and there is a second association relationship between the timeunit subset and the second time unit. Optionally, the first conditionfurther includes that the downlink aggregation parameter is greaterthan 1. Optionally, the first preset value is greater than 1.

Optionally, the first preset value is the number of bits of feedbackinformation corresponding to a first time unit corresponding to afrequency domain unit in the semi-persistent codebook configuration. Inaddition, if the number of dynamically scheduled PDSCHs received in thetime unit subset is less than the first preset value, and all thesePDSCHs are located in the first time unit in the frequency domain unit,an NACK is set in a bit in the first codebook other than an ACK/NACK bitcorresponding to the PDSCH. This solution is mainly applied to a case inwhich a plurality of PDSCHs that do not overlap in time domain may bescheduled for one terminal device in one first time unit correspondingto one frequency domain unit. For example, one first time unit includes14 time domain symbols. It is preconfigured that a time domain locationin the first time unit includes the 1^(st) to the 7^(th) time domainsymbols and the 8^(th) to the 14^(th) time domain symbols. These twogroups of time domain locations do not overlap in time domain, and in anormal non-fallback semi-persistent codebook, the first time unitcorresponds to feedback of a 2-bit ACK/NACK. In this case, the firstpreset value is 2. The pre-configuration is performed by using RRCsignaling. Specifically, a time domain location to be actually scheduledis indicated by a time domain resource assignment indicator field on thePDCCH. For example, one bit on the PDCCH may be used to specificallyindicate one of the foregoing two groups of time domain locations.

In the foregoing optional solution, there may be the following twocases.

Case 1: When the number of dynamically scheduled PDSCHs received in thetime unit subset is 1, a size of the first codebook is equal to thefirst preset value, that is, the number of bits of feedback informationcorresponding to a first time unit corresponding to a frequency domainunit in the semi-persistent codebook configuration. An NACK is set in abit in the first codebook other than an ACK/NACK bit corresponding tothe PDSCH in the first codebook. For example, in the foregoing example,the first preset value is 2, the size of the first codebook is two bits,and an NACK is set in an ACK/NACK location corresponding to a timedomain location in which no PDSCH is received.

Case 2: When the number of dynamically scheduled PDSCHs received in thetime unit subset is 1, and all these PDSCHs are located in the firsttime unit in the frequency domain unit, a size of the first codebook isequal to the first preset value, that is, the number of bits of feedbackinformation corresponding to a first time unit corresponding to afrequency domain unit in the semi-persistent codebook configuration. Forexample, in the foregoing example, the first preset value is 2. If thenumber of dynamically scheduled PDSCHs received in the time unit subsetis 2, the size of the first codebook is two bits respectivelycorresponding to ACK/NACK feedback for PDSCHs in the foregoing twogroups of time domain locations.

Optionally, in this embodiment of this application, the secondassociation relationship is an association relationship determinedthrough the downlink control channel for dynamic scheduling.

For example, the second association relationship may be determined basedon timing indication information on a PDCCH. In other words, the secondassociation relationship is indicated to the terminal device by usingthe timing indication information on the PDCCH. The PDCCH includes 3-bittiming indication information, and the timing indication information isused to indicate a timing relationship between a slot in which a PDSCHscheduled through the PDCCH is located and a slot in which an ACK/NACKis located. For example, when the first association relationship is{n-1, n-2, n-3, n-4, n-5, n-6, n-7, n-8}, timing indication informationon a PDCCH is one of the eight values in the first associationrelationship.

Optionally, in this embodiment of this application, the preset conditionmay further include a second condition, the second condition is that avalue of indication information on a downlink control channel fordynamically scheduling the first downlink information is a second presetvalue, and the downlink control channel is a control channel forfallback scheduling.

In this embodiment of this application, for example, the second presetvalue may be a preset DAI value.

For example, the time unit subset includes a downlink slot 10 and adownlink slot 11. The first preset value, that is, the number of piecesof the first downlink information, in the first condition may be 1.

It is assumed that the second preset value is 1. A value of a DAIincluded on a PDCCH for scheduling a PDSCH in the downlink slot 10 is 1,and a value of a DAI included on a PDCCH for scheduling a PDSCH in thedownlink slot 11 is 2. If the terminal device misses detection of thePDCCH in the downlink slot 11, the terminal device detects only onescheduled PDSCH, and the first condition is met, that is, the number ofpieces of downlink control information is 1 (for example, when the firstpreset value is 1). The second preset value included in the downlinkslot 10 also meets the second condition and is 1. In this case, theterminal device sends an ACK/NACK corresponding to the PDSCH in thedownlink slot 10 to a base station. In this case, the base station andthe terminal device have a consistent understanding of a fallbackcodebook. To be specific, both the base station and the terminal deviceconsider that a 1-bit ACK/NACK in the fallback codebook corresponds to aPDSCH (for example, the PDSCH in the downlink slot 10) with a DAIbeing 1. This is not limited in this application.

Optionally, in this embodiment of this application, the downlink controlchannel may be a control channel for fallback scheduling.

In this embodiment of this application, for example, a downlink controlchannel for fallback scheduling may have at least one of the followingcharacteristics. For example, the downlink control channel for fallbackscheduling may be used for data scheduling performed before RRCestablishment; and none of values of all fields on the downlink controlchannel for fallback scheduling may be configured by using RRC dedicatedsignaling.

In this embodiment of this application, for example, the terminal devicemay be configured to detect a downlink control channel for non-fallbackscheduling. The control channel for non-fallback scheduling may have atleast one of the following characteristics, for example, the downlinkcontrol channel is used for data scheduling performed after RRCestablishment; and a value of at least one field in the control channelmay be configured by using RRC dedicated signaling.

For example, a time domain resource allocation field, a DAI field, a BWPindication field, and the like may be configured on the downlink controlchannel for non-fallback scheduling by using RRC dedicated signaling.

Optionally, indication information included on the downlink controlchannel for dynamically scheduling the first downlink information may bea DAI field, and the preset value is preferably DAI=1 or a valueindicated by a state ‘00’ of the DAI field.

Optionally, in this embodiment of this application, the preset conditionmay further include a third condition, and the third condition is thatthe first time unit in which the first downlink information is locatedis a first time unit in a specific time domain location in the time unitset.

Optionally, there may be one or more specific time domain locations.

In the following scenario: for a terminal device, there may be aplurality of candidate time domain locations in one slot correspondingto one carrier, the plurality of candidate time domain locations arepreconfigured by using RRC signaling or predefined according to astandard. The plurality of candidate time domain locations may overlapwith each other in time domain, but do not overlap in time domain inactual scheduling.

For example, one slot includes 14 time domain symbols. A plurality ofpreconfigured candidate time domain locations in one slot include afirst, second, third, and fourth candidate time domain locations. It isassumed that the candidate time domain locations are the 1^(st) to the4^(th) time domain symbols, the 3^(rd) to the 6^(th) time domainsymbols, the 7^(th) to the 10^(th) time domain symbols, and the 9^(th)to the 14^(th) time domain symbols, respectively. A maximum number ofcandidate time domain locations that do not overlap in time domain andthat are included in the four groups of time domain symbols is 2.Therefore, in a normal non-fallback semi-persistent codebook, twoACK/NACK bits are fed back in one slot corresponding to one carrier. Thefour groups of time domain locations that are preconfigured areconfigured by using RRC signaling. Specifically, a time domain locationto be actually scheduled is indicated by a time domain resourceassignment indicator field on the PDCCH. For example, two bits on thePDCCH may be used to specifically indicate one of the foregoing fourgroups of time domain locations.

Assuming that the first preset value is 1, codebook fallback isperformed only when one only PDSCH received by the terminal device inthe time unit subset is determined, or in other words, codebook fallbackis performed only when it is determined that a PDSCH in the first timeunit is a PDSCH scheduled in a specific time domain location in the timeunit set.

Therefore, optionally, if each candidate time domain location isconsidered as the first time unit, the specific time domain location maybe a specific first time unit in a plurality of first time units with amaximum number that are included in one slot and that do not overlap intime domain, or a first time unit overlapping with the specific firsttime unit in time domain in the slot.

Specifically, the plurality of first time units with a maximum numberthat are in the slot and that do not overlap in time domain are a firstand a third candidate time domain locations, and a specific first timeunit is determined according to a preset rule. For example, the specificfirst time unit is a first time unit with an earliest start time domainsymbol or a latest start time domain symbol in the plurality of firsttime units. For example, the specific first time unit is determined asthe first candidate time domain location, and a time domain locationoverlapping with the first candidate time domain location in time domainfurther includes the third candidate time domain location. When thereare a plurality of candidate time domain locations overlapping in timedomain, only one candidate time domain location may be scheduled duringactual scheduling. Therefore, the first time units corresponding to thefirst and the third candidate time domain locations may be used as thespecific time domain location.

In this embodiment of this application, it is assumed that the firstpreset value in the first condition included in the preset condition is1, and the third condition is that the first time unit in the specifictime domain location is an earliest downlink slot.

For example, if the number of dynamically scheduled PDSCHs received bythe terminal device in a downlink slot subset corresponding to theuplink slot i is equal to the first preset value 1, and a downlink slotin which the dynamically scheduled PDSCH is located is a preset timedomain location in the downlink slot set, that is, an earliest downlinkslot in the downlink slot set, an ACK/NACK codebook may include only anACK/NACK corresponding to the PDSCH in the downlink slot 1, and does notinclude an ACK/NACK corresponding to another downlink slot in thedownlink slot set corresponding to the uplink slot i.

Optionally, in this embodiment of this application, the preset conditionmay further include a fourth condition, and the fourth condition is thatthe first downlink information is carried in a primary frequency domainunit or a first secondary frequency domain unit in the at least onefrequency domain unit.

For example, a plurality of carriers may be configured for the terminaldevice, and codebook fallback may be based on whether a PDSCH isscheduled. In this case, a predetermined carrier may be selected for thePDSCH. For example, the predetermined carrier may be a primary carrier,a primary bandwidth part, a primary secondary carrier, or a primarysecondary bandwidth part.

A carrier is used as an example. The primary secondary carrier may be aprimary carrier in a secondary carrier group in a dual connection mode,or the primary secondary carrier may be a secondary carrier carrying aPUCCH.

It should be understood that in this embodiment of this application, thepreset condition may further include any one or more of the secondcondition, the third condition, and the fourth condition in addition tothe first condition. For example, the preset condition further includesthe second condition and the third condition in addition to the firstcondition. Alternatively, the preset condition further includes thesecond condition and the fourth condition in addition to the firstcondition. This is not limited in this application.

Optionally, the value of the indication information is set according toa predefined rule related to the time unit subset.

In other words, the value of the indication information included on thedownlink control channel corresponding to the first downlink informationincluded in the time unit subset is set according to the predefinedrule, and the preset rule is not related to a value of indicationinformation included on a downlink control channel corresponding todownlink information in a time unit in the time unit set other than thetime unit subset.

For example, a downlink slot set includes a downlink slot 1 to adownlink slot 8, that is, the time unit set includes the downlink slots1 to 8. A downlink slot subset corresponding to an uplink slot includesthe downlink slot 1 and the downlink slot 2, that is, the time unitsubset includes the downlink slot 1 and the downlink slot 2. A value ofthe indication information is related to a value of indicationinformation included on a downlink control channel for scheduling aPDSCH in the downlink slot 1 and the downlink slot 2, and is not relatedto a value of indication information included on a downlink controlchannel for scheduling a PDSCH in the downlink slot 3 to the downlinkslot 8.

It should be understood that in this embodiment of this application, avalue of indication information may be a value of a DAI.

Optionally, in this embodiment of this application, for at least onefirst time unit that corresponds to each of the at least one frequencydomain unit and that is in the first time unit subset, the predefinedrule is performing cumulative counting in a sequential order of timeunits.

For example, the preset rule may be that a value of indicationinformation of at least one time unit in a time unit subsetcorresponding to a first frequency domain unit may be counted as{1,2,3,4, 1,2,3,4, . . . }, and a value of indication information of atleast one time unit in a time unit subset corresponding to a secondfrequency domain unit may be counted as {1,2,3,4, 1,2,3,4, . . . }. Thisis not limited in this application. It should be noted that the numberof bits in a DAI field is usually 2. Therefore, there are only fourstates: ‘00’, ‘01’, ‘10’, and ‘11’, and corresponding values may be 1,2, 3, and 4, respectively, or 0, 1, 2, and 3, respectively. That thevalues are 1, 2, 3, and 4 is used as an example. If a value exceeds 4,cyclic counting may be performed. For example, the foregoing counts{1,2,3,4, 1,2,3,4, . . . } are actual counts {1,2,3,4, 5,6,7,8, . . . }.

Optionally, in this embodiment of this application, for at least onefirst time unit that corresponds to the at least one frequency domainunit and that is in the first time unit subset, the predefined rule isperforming cumulative counting first in a frequency-domain order andthen in a time-domain order.

For example, the preset rule may be that a time unit 1 corresponding toa frequency domain unit 1 is identified as 1, a time unit 1corresponding to a frequency domain unit 2 is identified as 2, a timeunit 1 corresponding to a frequency domain unit 3 is identified as 3,and so on. Then, a time unit 2 corresponding to the frequency domainunit 1 is identified as 4, a time unit 2 corresponding to the frequencydomain unit 2 is identified as 5, a time unit 2 corresponding to thefrequency domain unit 3 is identified as 6, and so on. In other words,the preset rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

In this embodiment of this application, a problem of inconsistentunderstanding between a terminal device and a base station that may becaused due to codebook fallback is resolved through independent DAIcumulative counting in a slot sub set.

Optionally, in this embodiment of this application, the firstassociation relationship is predefined according to a standard and/orconfigured for the terminal device by the network device by using RRCsignaling.

S440: The terminal device sends uplink control information in the secondtime unit, where the uplink control information carries the firstcodebook.

In other words, the terminal device sends the first codebook in thesecond time unit, and the second time unit may be an uplink time unit.

Optionally, the second time unit may be an uplink time unit or aflexible time unit. In this embodiment of this application, an uplinkslot is used as an example for description.

It should be noted that the terminal device may send, in the second timeunit, a signal obtained through decoding/modulation by using the firstcodebook.

Optionally, in this embodiment of this application, the at least onepiece of downlink information may further include second downlinkinformation, where a downlink control channel for scheduling the seconddownlink information is a downlink control channel for semi-persistentscheduling, and the first codebook further includes feedback informationcorresponding to the second downlink information.

Optionally, in this embodiment of this application, before the terminaldevice determines the first codebook, the terminal device determines asemi-persistent codebook mode from a plurality of candidate codebookmodes, where the plurality of candidate codebook modes include asemi-persistent codebook mode and a dynamic codebook mode.

Optionally, in this embodiment of this application, before the terminaldevice sends the feedback information in the second time unit based onthe first codebook, the terminal device determines a target resource setof an uplink control channel, and determines a target resource of theuplink control channel from the target resource set. The terminal devicesends the uplink control information on the target resource in thesecond time unit, where the uplink control information carries the firstcodebook.

For example, when the number of pieces of the first downlink informationin the at least one piece of downlink information is equal to the firstpreset value (for example, the first preset value is 1) or when theforegoing other conditions are met, that is, the first codebook in thiscase is a fallback codebook, the target resource set is a first resourceset, and a codebook size of the first codebook corresponding to thefirst resource set is less than or equal to 2.

In other words, when the number of pieces of the first downlinkinformation, which may be the number of PDSCHs, meets the firstcondition included in the preset condition, for example, when the firstpreset value is 1, that is, the terminal device detects a PDCCH for onescheduled PDSCH, the terminal device may perform codebook fallback. Inthis case, the terminal device sends the first codebook of the feedbackinformation on a first target resource in the first resource set.

Optionally, in this embodiment of this application, when the number ofpieces of the first downlink information in the at least one piece ofdownlink information is not the first preset value, the target resourceset is a second resource set, and a codebook size of the first codebookcorresponding to the second resource set is greater than 2. In thiscase, the first codebook is a non-fallback codebook or a normalsemi-persistent codebook. In this case, the terminal device sends thefirst codebook of the feedback information on a second target resourcein the second resource set.

It should be understood that in this embodiment of this application, thefirst downlink information may alternatively be dynamically scheduleddownlink information.

For example, the first downlink information may include downlink SPSrelease indication or a dynamically scheduled downlink data channel,where a dynamically scheduled downlink data channel may be dynamicallyscheduled through a downlink control channel.

It should be noted that dynamic scheduling means that each transmissionof a downlink data channel needs to be scheduled through a correspondingdownlink control channel.

A dynamically scheduled downlink data channel corresponds to asemi-persistently scheduled downlink data channel that is scheduledthrough a semi-persistent downlink control channel. To be specific,after a semi-persistent downlink control channel is sent once, acorresponding semi-persistent downlink data channel may be always sentaccording to a preconfigured sending cycle, with no need to send thesemi-persistent downlink control channel each time.

Semi-persistent downlink scheduling may be released through a specificdownlink control channel. A downlink control channel used to implementrelease indication of the semi-persistent downlink scheduling is usuallynot used to schedule a downlink data channel. However, the terminaldevice also feeds back ACK/NACK feedback information for the downlinkcontrol channel.

It should be understood that in this embodiment of this application, adynamically scheduled downlink data channel may alternatively be used asan example for describing downlink information. This is not limited inthis application.

Optionally, in this embodiment of this application, in the dynamiccodebook mode, the terminal device may determine a second codebook offeedback information, where the second codebook includes feedbackinformation corresponding to an actually scheduled first time unit inthe time unit set.

In this embodiment of this application, in the semi-persistent codebookmode, for a slot in which feedback information is sent, when a pluralityof pieces of downlink data are scheduled in a plurality of time units ina time unit set corresponding to the first association relationship,codebook fallback may be performed when the number of pieces of downlinkdata corresponding to the second association relationship sent in theslot is equal to the first preset value (for example, the first presetvalue is 1).

When other several conditions in the preset condition are met,performance of feedback information demodulation is improved.

FIG. 6 is a schematic diagram of a feedback information fallback modeaccording to an embodiment of this application.

It should be understood that in FIG. 6 , a single carrier is used as anexample for describing this embodiment. This embodiment of thisapplication may be extended to a case of a plurality of carriers.

In FIG. 6 , a downlink slot set (for example, a first time unit set)corresponding to an uplink slot i includes downlink slots 1 to 8. A basestation actually schedules a PDSCH for a terminal device in eachdownlink slot. A downlink slot set corresponding to an uplink slot jincludes slots 4 to 11. The base station actually schedules PDSCHs forthe terminal device in the downlink slots 4 to 8 and the downlink slots10 and 11, but does not schedule the downlink slot 9 for the terminaldevice.

The terminal device may feed back ACK/NACK information to the basestation in both the uplink slots i and j. There is a first associationrelationship between the uplink slot i and the downlink slots 1 to 8,and there is a first association relationship between the uplink slot jand the downlink slots 4 to 11. The first association relationship isspecifically a timing relationship between a candidate slot forscheduling a PDSCH and a slot for an ACK/NACK. Specifically, the firstassociation relationship may be predefined according to a standard ornotified by the base station to the terminal device by using RRCdedicated signaling.

A downlink slot subset corresponding to the uplink slot i includes thedownlink slots 1 to 8, and a downlink slot subset corresponding to theuplink slot j includes the downlink slots 10 and 11. It can be learnedthat the downlink slot subset corresponding to the uplink slot i is asubset of the downlink slot set corresponding to the uplink slot i, andthe downlink slot subset corresponding to the uplink slot j is a subsetof the downlink slot set corresponding to the uplink slot j.

For example, there is a second association relationship between theuplink slot i and the downlink slots 1 to 8, and there is a secondassociation relationship between the uplink slot j and the downlinkslots 10 and 11. The second association relationship is a timingrelationship between a slot in which an actually scheduled PDSCH islocated and the slot for the ACK/NACK. The timing relationship isdetermined by using timing indication information on a PDCCH foractually scheduling the PDSCH. In other words, the second associationrelationship is determined by using the timing indication information onthe PDCCH for dynamically scheduling the PDSCH.

In this embodiment of this application, for example, an example in whichan ACK/NACK is fed back in the uplink slot j is used to describe afeedback information fallback mode.

It is assumed that a first preset value is 1. If the number ofdynamically scheduled PDSCHs received by the terminal device in thedownlink slot subset corresponding to the uplink slot j is 1 (even ifthe terminal device receives a plurality of dynamically scheduled PDSCHsin the slot 4 to the slot 11 included in the downlink slot set), a firstcondition included in a preset condition is met. This is not limited inthis application.

For example, when a dynamically scheduled PDSCH in the downlink slot 10is received, but a PDCCH for dynamically scheduling a PDSCH in thedownlink slot 11 is undetected, an ACK/NACK codebook (that is, a firstcodebook) may include only an ACK/NACK corresponding to the PDSCH in thedownlink slot 10, and does not include an ACK/NACK corresponding toanother downlink slot in the slot 4 to the slot 11 in the downlink slotset corresponding to the uplink slot j. This is not limited in thisapplication.

For example, when PDCCHs for dynamically scheduling PDSCHs in thedownlink slot 10 and the downlink slot 11 is received, the number ofpieces of downlink information is 2. In this case, the first conditionincluded in the preset condition is not met, that is, the first presetvalue is not 1. In this case, the ACK/NACK codebook includes ACKs/NACKsin the downlink slots 4 to 11 in the downlink slot set. In other words,no codebook fallback is performed, and a normal semi-persistent codebookis used instead. This is not limited in this application.

To support codebook fallback, a value of the DAI field may be countedaccording to a preset rule, to avoid a possible error during codebookfallback.

For example, it is assumed that both DAIS on PDCCHs corresponding to thedownlink slots 10 and 11 are set to be a preset value 1. If the terminaldevice misses detection of the PDCCH corresponding to the downlink slot10, the terminal device sends, by using a fallback codebook, a 1-bitACK/NACK corresponding to the downlink slot 11. Alternatively, if theterminal device misses detection of the PDCCH corresponding to thedownlink slot 11, the terminal device sends, by using a fallbackcodebook, a 1-bit ACK/NACK corresponding to the downlink slot 10.However, a base station does not know which PDCCH is undetected by theterminal device. Therefore, the base station has a fuzzy understandingof a downlink slot corresponding to the fallback codebook.

A value of a DAI included on a PDCCH corresponding to a dynamicallyscheduled PDSCH in the downlink slot subset may be set according to apreset rule.

In addition, codebook fallback only occurs in a slot subsetcorresponding to the timing indication information or the secondassociation relationship. Therefore, the preset rule is not related to avalue of a DAI included on a PDCCH corresponding to a PDSCH in a slot ina slot set other than a slot subset.

For example, for a value of a DAI in the downlink slot subsetcorresponding to the uplink slot j, a rule is performing cumulativecounting from the preset value in a time order. To be specific, thedownlink slot 10 corresponds to DAI=1, and the downlink slot 11 iscorresponding DAI=2.

Optionally, for at least one downlink slot corresponding to each of atleast one carrier in a downlink slot subset (for example, a time unitsubset), the preset rule may be performing cumulative counting in asequential order of downlink slots; or for at least one downlink slotcorresponding to the at least one carrier in the downlink slot subset,the preset rule may be performing cumulative counting first in afrequency-domain order and then in a time-domain order.

For example, the preset rule may be that a value of indicationinformation of at least one time unit corresponding to a time unitsubset in a first frequency domain unit may be counted as {1,2,3,4,1,2,3,4, . . . }, and a value of indication information of at least onetime unit in a time unit subset corresponding to a second frequencydomain unit may be counted as {1,2,3,4, 1,2,3,4, . . . }. This is notlimited in this application. It should be noted that the number of bitsin a DAI field is usually 2. Therefore, there are only four states:‘00’, ‘01’, ‘10’, and ‘11’, and corresponding values may be 1, 2, 3, and4, respectively, or 0, 1, 2, and 3, respectively. That the values are 1,2, 3, and 4 is used as an example. If a value exceeds 4, cyclic countingmay be performed. For example, the foregoing counts {1,2,3,4, 1,2,3,4, .. . } are actual counts {1,2,3,4, 5,6,7,8, . . . }.

For another example, the preset rule may be that a time unit 1corresponding to a frequency domain unit 1 is identified as 1, a timeunit 1 corresponding to a frequency domain unit 2 is identified as 2, atime unit 1 corresponding to a frequency domain unit 3 is identified as3, and so on. Then, a time unit 2 corresponding to the frequency domainunit 1 is identified as 4, a time unit 2 corresponding to the frequencydomain unit 2 is identified as 5, a time unit 2 corresponding to thefrequency domain unit 3 is identified as 6, and so on. In other words,the preset rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

There may be a second association relationship between the time unitsubset and a second time unit. Not all slots in which actually scheduledPDSCHs are located in the downlink slot set correspond to the uplinkslot j based on the timing indication information.

For example, the actually scheduled downlink slots 4 to 8 in the setcorrespond to the uplink slot i based on the timing indicationinformation, but only the downlink slots 10 and 11 in the set correspondto the uplink slot j based on the timing indication information.Therefore, the terminal device may determine, based on only whether thenumber of dynamically scheduled PDSCHs in the subset is equal to thefirst preset value, whether to perform codebook fallback.

Optionally, the preset condition meeting the codebook fallback mayfurther include the following conditions.

Optionally, the preset condition further includes a second condition,and the second condition is that a value of indication information on adownlink control channel for dynamically scheduling the first downlinkinformation is a second preset value.

For example, a value of a DAI included on a received PDCCH fordynamically scheduling only one PDSCH in a slot subset is a secondpreset value.

For example, the second preset value is 1. A value of a DAI included ona PDCCH for scheduling a PDSCH in the downlink slot 10 is 1, and a valueof a DAI included on a PDCCH for scheduling a PDSCH in the downlink slot11 is 2. If the terminal device misses detection of the PDCCH in thedownlink slot 11, the terminal device detects only one scheduled PDSCH,and the first condition is met, that is, the number of pieces ofdownlink control information is 1 (for example, when the first presetvalue is 1). The second preset value included in the PDCCH forscheduling the PDSCH in the downlink slot 10 also meets the secondcondition and is 1. In this case, the terminal device sends an ACK/NACKcorresponding to the PDSCH in the downlink slot 10 to a base station. Inthis case, the base station can learn, based on DAI values in differentdownlink slots, that the sent feedback information corresponds to thePDSCH in the downlink slot 10. This is not limited in this application.

It should be understood that a PDCCH for scheduling a PDSCH includes aDAI value. Therefore, both the terminal device and the base station candetermine a DAI value corresponding to any downlink slot.

If the second condition is not used, the base station cannot determinewhether the terminal device misses detection of a PDCCH corresponding tothe downlink slot 10 or the downlink slot 11. Therefore, a problem ofinconsistent understanding between the base station and the terminaldevice with respect to a downlink slot corresponding to a fallbackcodebook is caused.

That the second preset value may be 1 is also based on a case in whichbits in a DAI are limited. For example, specific states of a 2-bit DAImay be {00,01,10,11}.

In this case, four values that are different from each other, forexample, {1,2,3,4}, may be identified. Considering that a probabilitythat four consecutive PDCCHs are not detected is very low, a DAI cyclemay be used to represent more values. For example, {00,01,10,11,00,01,10,11, . . . } is used to represent values {1,2,3,4, 1,2,3,4, . .. }.

It should be understood that in this embodiment of this application, acorrespondence between another state and a value is not limited. Forexample, the values may be identified as {0,1,2,3, 0,1,2,3, . . . },that is, the values may be identified starting from 0.

It should be noted that, using FIG. 6 as an example, it is assumed thatdownlink slots {1, 2, 3, 4, 5, 6, 7, 8} may be represented as {1,2,3,4,1,2,3,4} by using a DAI cycle.

If the base station dynamically schedules five downlink slots:{1,2,3,4,5}, the downlink slots {1,2,3,4} are not detected by theterminal device, only a PDCCH corresponding to a dynamically scheduledPDSCH in the downlink slot 5 is detected. In this case, the first presetvalue is 1. If the second preset value is 1, a DAI value of thedynamically scheduled PDSCH in the downlink slot 5 is also equal to thesecond preset value. In this case, the PDSCH in the downlink slot 5meets conditions corresponding to both the first preset value and thesecond preset value, and a terminal device sends feedback information ofthe dynamically scheduled PDSCH in the downlink slot 5 to the basestation.

In this case, the base station cannot learn a downlink slot undetectedby the terminal device. Therefore, after the base station receivesfeedback information, the base station cannot determine whether thefeedback information is feedback information of a dynamically scheduledPDSCH in the downlink slot 2 or the downlink slot 6. In this case, theremay be a problem of inconsistent understanding between the base stationand the terminal device with respect to a downlink slot corresponding toa fallback codebook. However, in this embodiment of this embodiment, aprobability that four consecutive PDCCHs are not detected is very low.Therefore, there is no problem of inconsistent understanding between thebase station and the terminal device with respect to a downlink slotcorresponding to a fallback codebook.

Optionally, the preset condition further includes a fourth condition,and the fourth condition is that the first downlink information iscarried in a primary frequency domain unit or a first secondaryfrequency domain unit in the at least one frequency domain unit.

In this embodiment of this embodiment, a plurality of carriers may beconfigured for the terminal device, and codebook fallback may bedetermined based on whether a PDSCH is scheduled. In this case, apredetermined carrier may be selected for the PDSCH.

For example, the predetermined carrier may be a primary carrier, aprimary bandwidth part, a primary secondary carrier, or a primarysecondary bandwidth part.

A carrier is used as an example. The primary secondary carrier may be aprimary carrier in a secondary carrier group in a dual connection mode,or the primary secondary carrier may be a secondary carrier carrying aPUCCH.

Optionally, the fallback codebook is applicable to a case in which anSPS PDSCH exists.

For example, if only one dynamically scheduled PDSCH and one SPS PDSCHmay be received in the downlink slot subset, the terminal device canstill perform ACK/NACK feedback by using the fallback codebook. Thefallback codebook may include only one ACK/NACK bit corresponding to onedynamically scheduled PDSCH and one ACK/NACK bit corresponding to oneSPS PDSCH.

In an LTE system, if one dynamically scheduled PDSCH and one SPS PDSCHare received, only a special feedback mode of channel selection can beused. In a 5G system, however, a fallback codebook may be used in thiscase.

There may be ACK/NACK resource indication information, for example, apreconfigured DAI, on a PDCCH for dynamically scheduling a PDSCH.

ACKs/NACKs respectively corresponding to the dynamically scheduled PDSCHand the SPS PDSCH may be carried on an indicated PUCCH resource.

FIG. 7 is a schematic diagram of a feedback information fallback modeaccording to an embodiment of this application.

It should be understood that in FIG. 7 , a single carrier is used as anexample for describing this embodiment. This embodiment of thisapplication may be extended to a case of a plurality of carriers.

In this embodiment of this application, for example, a downlink slot setcorresponding to an uplink slot i includes downlink slots 1 to 8, and abase station actually schedules a PDSCH for a terminal device only inthe downlink slot 1; and a downlink slot set corresponding to an uplinkslot j includes downlink slots 4 to 11, and the base station actuallyschedules a PDSCH for the terminal device only in the downlink slot 10.

The terminal device feeds back ACK/NACK information to the base stationin both the uplink slot i and the uplink slot j. There is a firstassociation relationship between the uplink slot i and the downlinkslots 1 to 8, and there is a first association relationship between theuplink slot j and the downlink slots 4 to 11. Specifically, the firstassociation relationship may be shown in FIG. 3 . This is not limited inthis application.

As described in FIG. 7 , a downlink slot subset corresponding to theuplink slot i includes the downlink slots 1 to 8, and a downlink slotsubset corresponding to the uplink slot j includes the downlink slots 10and 11.

It can be learned that the downlink slot subset corresponding to theuplink slot i is a subset of the downlink slot set corresponding to theuplink slot i, and the downlink slot subset corresponding to the uplinkslot j is a subset of the downlink slot set corresponding to the uplinkslot j.

Specifically, there is a second association relationship between theuplink slot i and the downlink slots 1 to 8. Specifically, the secondassociation relationship may be shown in FIG. 3 . This is not limited inthis application.

Optionally, in this embodiment of this application, a preset conditionfurther includes a third condition, and the third condition is that afirst time unit in which the first downlink information is located is afirst time unit in a specific time domain location in the time unit set.

Based on the third condition, no limitation needs to be imposed on adownlink control channel in a manner the same as that in the embodimentshown in FIG. 6 , because dependence on a DAI value may not be required.

In other words, a downlink control channel for dynamically schedulingthe first downlink information may be a downlink control channel forfallback scheduling, or a downlink control channel for non-fallbackscheduling.

For the first time unit in the specific time domain location, it may beunderstood that once the time unit set is determined, the specific timedomain location is an absolute time domain location in the time unitset.

For example, the first time unit may be preset to be an earliest timeunit or a latest time unit in the time unit set. This is not limited inthis application.

For example, an ACK/NACK fed back in the uplink slot i is used as anexample for description.

Assuming that a first preset value in a first condition included in thepreset condition is 1, codebook fallback is performed when the number ofpieces of first downlink information is 1.

If the number of dynamically scheduled PDSCHs received by the terminaldevice in the downlink slot subset corresponding to the uplink slot i isa first preset value, for example, the first preset value is 1, and adownlink slot 1 in which the dynamically scheduled PDSCH is located is apreset time domain location in the downlink slot set (for example, thethird condition is that the first time unit in the specific time domainlocation is an earliest downlink slot), an ACK/NACK codebook may includeonly an ACK/NACK corresponding to the PDSCH in the downlink slot 1, anddoes not include an ACK/NACK corresponding to another downlink slot inthe downlink slot set corresponding to the uplink slot i.

If the number of dynamically scheduled PDSCHs received by the terminaldevice in the downlink slot subset corresponding to the slot i is afirst preset value, for example, the first preset value is 1, and adownlink slot 1 in which the dynamically scheduled PDSCH is located isnot a preset time domain location in the downlink slot set, that is, thethird condition included in the preset condition is not met, an ACK/NACKcodebook includes ACKs/NACKs corresponding to all PDSCHs in the downlinkslot 1 to the downlink slot 8.

For example, an ACK/NACK fed back in the uplink slot j is used as anexample for description.

Assuming that the first preset value in the first condition included inthe preset condition is 1, codebook fallback is performed when thenumber of pieces of the first downlink information is 1.

If the number of dynamically scheduled PDSCHs received by the terminaldevice in the downlink slot set corresponding to the uplink slot j is afirst preset value, for example, a dynamically scheduled PDSCH in thedownlink slot 10 is received, but the downlink slot 10 in which thedynamically scheduled PDSCH is located is not a preset time domainlocation in the downlink slot set (for example, the third condition isthat the first time unit in the specific time domain location is theearliest downlink slot 4), an ACK/NACK codebook is a normalsemi-persistent codebook, that is, the ACK/NACK codebook needs toinclude ACKs/NACKs corresponding to all the downlink slots 4 to 11 inthe downlink slot set.

Optionally, the preset condition further includes a fourth condition,and the fourth condition is that the first downlink information iscarried in a primary frequency domain unit or a first secondaryfrequency domain unit in the at least one frequency domain unit.

In this embodiment of this embodiment, a plurality of carriers may beconfigured for the terminal device, and codebook fallback may bedetermined based on whether a PDSCH is scheduled. In this case, apredetermined carrier may be selected for the PDSCH.

For example, the predetermined carrier may be a primary carrier, aprimary bandwidth part, a primary secondary carrier, or a primarysecondary bandwidth part.

A carrier is used as an example. The primary secondary carrier may be aprimary carrier in a secondary carrier group in a dual connection mode,or the primary secondary carrier may be a secondary carrier carrying aPUCCH.

Optionally, in this embodiment of this application, the preset conditionmay alternatively include both the second condition and the thirdcondition. In other words, the value of the indication information onthe downlink control channel for dynamically scheduling the firstdownlink information is the second preset value, and the first time unitin which the first downlink information is located is the first timeunit in the specific time domain location in the time unit set. In thiscase, based on the second preset value and the first time unit in thespecific time domain location, consistency of downlink slotunderstanding between the terminal device and a base station duringcodebook fallback is improved.

For example, it is assumed that the first preset value in the firstcondition included in the preset condition is 1, the second condition isthat the second preset value is 1, and the third condition is that thefirst time unit in the specific time domain location is an earliestdownlink slot (for example, the downlink slot 4).

An ACK/NACK fed back in the uplink slot j is used as an example fordescription.

If the terminal device receives a dynamically scheduled PDSCH in thedownlink slot 10 in the downlink slot subset corresponding to the slotj, and misses detection of PDCCH corresponding to a dynamicallyscheduled PDSCH in the downlink slot 11, a DAI value on the PDCCH in thedownlink slot 10 is 1, and a DAI value on the PDCCH in the downlink slot11 is 2. The terminal cannot receive the PDCCH with the DAI value being2 in the downlink slot 11 because the terminal device misses detectionof the PDCCH in the downlink slot 11. In this case, the scheduled PDSCHin the downlink slot 10 meets the first condition and the secondcondition, but does not meet the third condition that the first timeunit in the time domain location is an earliest downlink slot.Therefore, an ACK/NACK codebook is a normal semi-persistent codebook,that is, the ACK/NACK codebook needs to include ACKs/NACKs correspondingto all the downlink slots 4 to 11 in the downlink slot set.

Optionally, the fallback codebook is applicable to a case in which anSPS PDSCH exists.

For example, if only one dynamically scheduled PDSCH and one SPS PDSCHmay be received in the downlink slot subset, the terminal device canstill perform ACK/NACK feedback by using the fallback codebook. Thefallback codebook may include only one ACK/NACK bit corresponding to onedynamically scheduled PDSCH and one ACK/NACK bit corresponding to oneSPS PDSCH.

In an LTE system, if one dynamically scheduled PDSCH and one SPS PDSCHare received, only a special feedback mode of channel selection can beused. In a 5G system, however, a fallback codebook may be used in thiscase.

There may be ACK/NACK resource indication information, for example, apreconfigured DAI, on a PDCCH for dynamically scheduling a PDSCH.ACKs/NACKs respectively corresponding to the dynamically scheduled PDSCHand the SPS PDSCH may be carried on an indicated PUCCH resource.

It should be understood that sequence numbers of the foregoing processesdo not mean execution sequences in various embodiments of thisapplication. The execution sequences of the processes should bedetermined according to functions and internal logic of the processes,and should not be construed as any limitation on the implementationprocesses of the embodiments of this application.

The foregoing describes in detail the feedback information transmissionmethod according to the embodiments of this application. In thisapplication, based on the semi-persistent codebook mode, when theterminal device schedules a plurality of pieces of downlink informationin at least one time unit for sending feedback information,specifically, in a plurality of time units in the time unit setcorresponding to the first association relationship, when the number ofpieces of downlink information corresponding to the second associationrelationship meets the first condition, codebook fallback can beperformed, thereby improving efficiency of utilizing, by a system, aresource of an uplink control channel that carries feedback information.It should be understood that the terminal device and the network devicein the embodiments of this application may perform the methods in theforegoing embodiments of this application. Therefore, for specificworking processes of the following products, reference may be made tocorresponding processes in the foregoing method embodiments.

FIG. 8 is a schematic structural diagram of a communication device 700according to an embodiment of this application. The communication device700 may be a terminal device applied to the system shown in FIG. 1 . Asshown in FIG. 8 , the communication device 700 includes a transceiverunit 710 and a processing unit 720.

The transceiver unit 710 and the processing unit 720 communicate witheach other through an internal connection channel, to transfer a controlsignal and/or a data signal. In a possible design, the transceiver unit710 and the processing unit 720 may be implemented by using a chip, toimplement corresponding functions of a terminal device in thisembodiment of this application.

In this embodiment of this application, the transceiver unit 710 isconfigured to:

receive at least one piece of downlink information in at least one firsttime unit in a time unit set, where the time unit set is a set of atleast one first time unit corresponding to at least one frequency domainunit configured for the terminal device.

The processing unit 720 is configured to:

determine a second time unit, where the second time unit is used tocarry feedback information corresponding to the at least one piece ofdownlink information, and there is a first association relationshipbetween the time unit set and the second time unit; and determine afirst codebook, where when first downlink information in a time unitsubset meets a preset condition, the first codebook includes feedbackinformation corresponding to the first downlink information, the firstcodebook does not include feedback information corresponding to aspecific time unit in the time unit subset, the specific time unit is atleast one first time unit in the time unit set other than a first timeunit in which the first downlink information is located, the presetcondition includes a first condition, the first condition is that thenumber of pieces of first downlink information is equal to a firstpreset value, the time unit subset is a subset of the time unit set, andthere is a second association relationship between the time unit subsetand the second time unit.

The transceiver unit 710 is configured to:

send uplink control information in the second time unit, where theuplink control information carries the first codebook.

Optionally, the processing unit 720 is further configured to:

determine a semi-persistent codebook mode from a plurality of candidatecodebook modes, where the plurality of candidate codebook modes includea semi-persistent codebook mode and a dynamic codebook mode.

Optionally, the preset condition further includes a second condition,and the second condition is that a value of indication information on adownlink control channel for dynamically scheduling the first downlinkinformation is a second preset value.

Optionally, the preset condition further includes a third condition, andthe third condition is that the first time unit in which the firstdownlink information is located is a first time unit in a specific timedomain location in the time unit set.

Optionally, the preset condition further includes a fourth condition,and the fourth condition is that the first downlink information iscarried in a primary frequency domain unit or a first secondaryfrequency domain unit in the at least one frequency domain unit.

Optionally, in this embodiment of this application, the preset conditionmay alternatively include both the second condition and the thirdcondition. In other words, the value of the indication information onthe downlink control channel for dynamically scheduling the firstdownlink information is the second preset value, and the first time unitin which the first downlink information is located is the first timeunit in the specific time domain location in the time unit set. In thiscase, based on the second preset value and the first time unit in thespecific time domain location, consistency of downlink slotunderstanding between the terminal device and a base station duringcodebook fallback is improved.

It should be understood that in this embodiment of this application, thepreset condition may further include any one or more of the secondcondition, the third condition, and the fourth condition in addition tothe first condition. For example, the preset condition further includesthe second condition and the third condition in addition to the firstcondition; or the preset condition further includes the second conditionand the fourth condition in addition to the first condition. This is notlimited in this application.

Optionally, when the number of pieces of the first downlink informationin the time unit subset does not meet the first condition, the firstcodebook includes feedback information corresponding to all first timeunits in the time unit set.

Optionally, the value of the indication information is set according toa predefined rule related to the time unit subset.

Optionally, for at least one first time unit that corresponds to each ofthe at least one frequency domain unit and that is in the first timeunit subset, the predefined rule is performing cumulative counting in asequential order of time units; or

for at least one first time unit that corresponds to the at least onefrequency domain unit and that is in the first time unit subset, thepredefined rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

For example, the preset rule may be that a value of indicationinformation of at least one time unit in a time unit subsetcorresponding to a first frequency domain unit may be counted as{1,2,3,4, 1,2,3,4, . . . }, and a value of indication information of atleast one time unit in a time unit subset corresponding to a secondfrequency domain unit may be counted as {1,2,3,4, 1,2,3,4, . . . }. Thisis not limited in this application. It should be noted that the numberof bits in a DAI field is usually 2. Therefore, there are only fourstates: ‘00’, ‘01’, ‘10’, and ‘11’, and corresponding values may be 1,2, 3, and 4, respectively, or 0, 1, 2, and 3, respectively. That thevalues are 1, 2, 3, and 4 is used as an example. If a value exceeds 4,cyclic counting may be performed. For example, the foregoing counts{1,2,3,4, 1,2,3,4, . . . } are actual counts {1,2,3,4, 5,6,7,8, . . . }.

For another example, the preset rule may be that a time unit 1corresponding to a frequency domain unit 1 is identified as 1, a timeunit 1 corresponding to a frequency domain unit 2 is identified as 2, atime unit 1 corresponding to a frequency domain unit 3 is identified as3, and so on. Then, a time unit 2 corresponding to the frequency domainunit 1 is identified as 4, a time unit 2 corresponding to the frequencydomain unit 2 is identified as 5, a time unit 2 corresponding to thefrequency domain unit 3 is identified as 6, and so on. In other words,the preset rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

Optionally, the at least one piece of downlink information furtherincludes second downlink information, where a downlink control channelfor scheduling the second downlink information is a downlink controlchannel for semi-persistent scheduling, and the first codebook furtherincludes feedback information corresponding to the second downlinkinformation.

Optionally, the first association relationship is predefined accordingto a standard and/or configured for the terminal device by a networkdevice by using RRC signaling.

Optionally, the second association relationship is determined based onthe downlink control channel for dynamic scheduling.

Optionally, a time unit may be at least one of a slot, a mini-slot, anda subframe.

Optionally, a frequency domain unit may be a carrier or a carrier BWP.

Optionally, the second time unit may be an uplink time unit or aflexible time unit.

Optionally, the first association relationship may be preconfigured, ornotified to the terminal device by using RRC dedicated signaling.Generally, for fallback PDCCH scheduling, the first associationrelationship may be preconfigured. For non-fallback PDCCH scheduling,the first association relationship may be notified to the terminaldevice by using RRC dedicated signaling.

Optionally, in this embodiment of this application, the downlink controlchannel may be a control channel for fallback scheduling.

Optionally, the indication information included on the downlink controlchannel for dynamically scheduling the first downlink information may bea DAI field, and the preset value is preferably DAI=1 or a valueindicated by a state ‘00’ of the DAI field.

Optionally, in this embodiment of this application, the at least onepiece of downlink information may further include second downlinkinformation, where a downlink control channel for scheduling the seconddownlink information is a downlink control channel for semi-persistentscheduling, and the first codebook further includes feedback informationcorresponding to the second downlink information.

Optionally, in this embodiment of this application, before the terminaldevice determines the first codebook, the terminal device determines asemi-persistent codebook mode from a plurality of candidate codebookmodes, where the plurality of candidate codebook modes include asemi-persistent codebook mode and a dynamic codebook mode.

Optionally, in this embodiment of this application, before the terminaldevice sends the feedback information in the second time unit based onthe first codebook, the terminal device determines a target resource setof an uplink control channel, and determines a target resource of theuplink control channel from the target resource set. The terminal devicesends the uplink control information on the target resource in thesecond time unit, where the uplink control information carries the firstcodebook.

For example, when the number of pieces of the first downlink informationin the at least one piece of downlink information is equal to the firstpreset value (for example, the first preset value is 1) or when theforegoing other conditions are met, that is, the first codebook in thiscase is a fallback codebook, the target resource set is a first resourceset, and a codebook size of the first codebook corresponding to thefirst resource set is less than or equal to 2.

In other words, when the number of pieces of the first downlinkinformation, which may be the number of PDSCHs, meets the firstcondition included in the preset condition, for example, when the firstpreset value is 1, that is, the terminal device detects a PDCCH for onescheduled PDSCH, the terminal device may perform codebook fallback. Inthis case, the terminal device sends the first codebook of the feedbackinformation on a first target resource in the first resource set.

Optionally, in this embodiment of this application, when the number ofpieces of the first downlink information in the at least one piece ofdownlink information is not the first preset value, the target resourceset is a second resource set, and a codebook size of the first codebookcorresponding to the second resource set is greater than 2. In thiscase, the first codebook is a non-fallback codebook or a normalsemi-persistent codebook. In this case, the terminal device sends thefirst codebook of the feedback information on a second target resourcein the second resource set.

It should be understood that in this embodiment of this application, thefirst downlink information may alternatively be dynamically scheduleddownlink information.

For example, the first downlink information may include downlink SPSrelease indication or a dynamically scheduled downlink data channel,where a dynamically scheduled downlink data channel may be dynamicallyscheduled through a downlink control channel.

It should be noted that dynamic scheduling means that each transmissionof a downlink data channel needs to be scheduled through a correspondingdownlink control channel.

A dynamically scheduled downlink data channel corresponds to asemi-persistently scheduled downlink data channel that is scheduledthrough a semi-persistent downlink control channel. To be specific,after a semi-persistent downlink control channel is sent once, acorresponding semi-persistent downlink data channel may be always sentaccording to a preconfigured sending cycle, with no need to send thesemi-persistent downlink control channel each time.

Semi-persistent downlink scheduling may be released through a specificdownlink control channel. A downlink control channel used to implementrelease indication of the semi-persistent downlink scheduling is usuallynot used to schedule a downlink data channel. However, the terminaldevice also needs to feed back ACK/NACK feedback information for thedownlink control channel.

It should be understood that in this embodiment of this application, adynamically scheduled downlink data channel may alternatively be used asan example for describing downlink information. This is not limited inthis application.

Optionally, in this embodiment of this application, in the dynamiccodebook mode, the terminal device may determine a second codebook offeedback information, where the second codebook includes feedbackinformation corresponding to an actually scheduled first time unit inthe time unit set.

It should be understood that although not shown, the communicationdevice 700 may further include another unit, such as an input unit andan output unit.

FIG. 9 is a structural block diagram of a communication device 800according to an embodiment of this application. The communication device800 may be a network device applied to the system shown in FIG. 1 . Thecommunication device 800 shown in FIG. 9 includes a transceiver unit 810and a processing unit 820.

The transceiver unit 810 and the processing unit 820 communicate witheach other through an internal connection channel, to transfer a controlsignal and/or a data signal. In a possible design, the transceiver unit810 and the processing unit 820 may be implemented by using a chip, toimplement corresponding functions of a network device in this embodimentof this application.

In this embodiment of this application, the transceiver unit 810 isconfigured to:

send at least one piece of downlink information to a terminal device inat least one first time unit in a time unit set, where the time unit setis a set of at least one first time unit corresponding to at least onefrequency domain unit configured for the terminal device.

The processing unit 820 is configured to:

determine a second time unit, where the second time unit is used tocarry feedback information corresponding to the at least one piece ofdownlink information, and there is a first association relationshipbetween the time unit set and the second time unit.

The transceiver unit 810 is configured to:

receive, in the second time unit, uplink control information sent by theterminal device, where the uplink control information carries a firstcodebook, the first codebook is a first codebook when first downlinkinformation in a time unit subset meets a preset condition, the firstcodebook includes feedback information corresponding to the firstdownlink information, the first codebook does not include feedbackinformation corresponding to a specific time unit in the time unitsubset, the specific time unit is at least one first time unit in thetime unit set other than a first time unit in which the first downlinkinformation is located, the preset condition includes a first condition,the first condition is that the number of pieces of first downlinkinformation is equal to a first preset value, the time unit subset is asubset of the time unit set, and there is a second associationrelationship between the time unit subset and the second time unit.

Optionally, the processing unit 820 is further configured to:

determine a semi-persistent codebook mode from a plurality of candidatecodebook modes, where the plurality of candidate codebook modes includea semi-persistent codebook mode and a dynamic codebook mode; and

The transceiver unit 810 is further configured to:

configure the semi-persistent codebook mode for the terminal device byusing signaling.

Optionally, the preset condition further includes a second condition,and the second condition is that a value of indication information on adownlink control channel for dynamically scheduling the first downlinkinformation is a second preset value.

Optionally, the preset condition further includes a third condition, andthe third condition is that the first time unit in which the firstdownlink information is located is a first time unit in a specific timedomain location in the time unit set.

Optionally, the preset condition further includes a fourth condition,and the fourth condition is that the first downlink information iscarried in a primary frequency domain unit or a first secondaryfrequency domain unit in the at least one frequency domain unit.

Optionally, in this embodiment of this application, the preset conditionmay alternatively include both the second condition and the thirdcondition. In other words, the value of the indication information onthe downlink control channel for dynamically scheduling the firstdownlink information is the second preset value, and the first time unitin which the first downlink information is located is the first timeunit in the specific time domain location in the time unit set. In thiscase, based on the second preset value and the first time unit in thespecific time domain location, consistency of downlink slotunderstanding between the terminal device and a base station duringcodebook fallback is improved.

It should be understood that in this embodiment of this application, thepreset condition may further include any one or more of the secondcondition, the third condition, and the fourth condition in addition tothe first condition. For example, the preset condition further includesthe second condition and the third condition in addition to the firstcondition. Alternatively, the preset condition further includes thesecond condition and the fourth condition in addition to the firstcondition. This is not limited in this application.

Optionally, when the number of pieces of the first downlink informationin the time unit subset does not meet the first condition, the firstcodebook includes feedback information corresponding to all first timeunits in the time unit set.

Optionally, the value of the indication information is set according toa predefined rule related to the time unit subset.

Optionally, for at least one first time unit that corresponds to each ofthe at least one frequency domain unit and that is in the first timeunit subset, the predefined rule is performing cumulative counting in asequential order of time units; or

for at least one first time unit that corresponds to the at least onefrequency domain unit and that is in the first time unit subset, thepredefined rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

For example, the preset rule may be that a value of indicationinformation of at least one time unit in a time unit subsetcorresponding to a first frequency domain unit may be counted as{1,2,3,4, 1,2,3,4, . . . }, and a value of indication information of atleast one time unit in a time unit subset corresponding to a secondfrequency domain unit may be counted as {1,2,3,4, 1,2,3,4, . . . }. Thisis not limited in this application. It should be noted that the numberof bits in a DAI field is usually 2. Therefore, there are only fourstates: ‘00’, ‘01’, ‘10’, and ‘11’, and corresponding values may be 1,2, 3, and 4, respectively, or 0, 1, 2, and 3, respectively. That thevalues are 1, 2, 3, and 4 is used as an example. If a value exceeds 4,cyclic counting may be performed. For example, the foregoing counts{1,2,3,4, 1,2,3,4, . . . } are actual counts {1,2,3,4, 5,6,7,8, . . . }.

For another example, the preset rule may be that a time unit 1corresponding to a frequency domain unit 1 is identified as 1, a timeunit 1 corresponding to a frequency domain unit 2 is identified as 2, atime unit 1 corresponding to a frequency domain unit 3 is identified as3, and so on. Then, a time unit 2 corresponding to the frequency domainunit 1 is identified as 4, a time unit 2 corresponding to the frequencydomain unit 2 is identified as 5, a time unit 2 corresponding to thefrequency domain unit 3 is identified as 6, and so on. In other words,the preset rule is performing cumulative counting first in afrequency-domain order and then in a time-domain order.

Optionally, the at least one piece of downlink information furtherincludes second downlink information, where a downlink control channelfor scheduling the second downlink information is a downlink controlchannel for semi-persistent scheduling, and the first codebook furtherincludes feedback information corresponding to the second downlinkinformation.

Optionally, the first association relationship is predefined accordingto a standard and/or configured for the terminal device by a networkdevice by using RRC signaling.

Optionally, the second association relationship is indicated by thedownlink control channel for dynamically scheduling the first downlinkinformation.

Optionally, a time unit may be at least one of a slot, a mini-slot, anda subframe.

Optionally, a frequency domain unit may be a carrier or a carrier BWP.

Optionally, the second time unit may be an uplink time unit or aflexible time unit.

Optionally, the first association relationship may be preconfigured, ornotified to the terminal device by using RRC dedicated signaling.Generally, for fallback PDCCH scheduling, the first associationrelationship may be preconfigured.

For non-fallback PDCCH scheduling, the first association relationshipmay be notified to the terminal device by using RRC dedicated signaling.

Optionally, in this embodiment of this application, the downlink controlchannel may be a control channel for fallback scheduling.

Optionally, the indication information included on the downlink controlchannel for dynamically scheduling the first downlink information may bea DAI field, and the preset value is preferably DAI=1 or a valueindicated by a state ‘00’ of the DAI field.

Optionally, in this embodiment of this application, the at least onepiece of downlink information may further include second downlinkinformation, where a downlink control channel for scheduling the seconddownlink information is a downlink control channel for semi-persistentscheduling, and the first codebook further includes feedback informationcorresponding to the second downlink information.

It should be understood that in this embodiment of this application, thefirst downlink information may alternatively be dynamically scheduleddownlink information.

For example, the first downlink information may include downlink SPSrelease indication or a dynamically scheduled downlink data channel,where a dynamically scheduled downlink data channel may be dynamicallyscheduled through a downlink control channel.

It should be noted that dynamic scheduling means that each transmissionof a downlink data channel needs to be scheduled through a correspondingdownlink control channel.

The dynamically scheduled downlink data channel corresponds to asemi-persistently scheduled downlink data channel that is scheduledthrough a semi-persistent downlink control channel. To be specific,after a semi-persistent downlink control channel is sent once, acorresponding semi-persistent downlink data channel may be always sentaccording to a preconfigured sending cycle, with no need to send thesemi-persistent downlink control channel each time.

Semi-persistent downlink scheduling may be released through a specificdownlink control channel. A downlink control channel used to implementrelease indication of the semi-persistent downlink scheduling is usuallynot used to schedule a downlink data channel. However, the terminaldevice also needs to feed back ACK/NACK feedback information for thedownlink control channel.

It should be understood that in this embodiment of this application, adynamically scheduled downlink data channel may alternatively be used asan example for describing downlink information. This is not limited inthis application.

Optionally, in this embodiment of this application, in the dynamiccodebook mode, the terminal device may determine a second codebook offeedback information, where the second codebook includes feedbackinformation corresponding to an actually scheduled first time unit inthe time unit set.

It should be understood that although not shown, the communicationdevice 800 may further include another unit, such as an input unit andan output unit.

FIG. 10 is a schematic block diagram of a communication device 900according to another embodiment of this application. As shown in FIG. 10, the communication device 900 may be a terminal device, or may be achip or a circuit, for example, a chip or a circuit that may be disposedin a terminal device. The terminal device may correspond to the terminaldevice in the foregoing method.

The communication device 900 may include a processor 11 (which may bethe processing unit 720) and a memory 12. The memory 12 is configured tostore an instruction, and the processor 11 is configured to execute theinstruction stored in the memory 12, so that the communication device900 implements the steps performed by the terminal device in the methodcorresponding to FIG. 4 .

The communication device 900 may further include an input port 13 (whichmay be the transceiver unit 710) and an output port 14 (which may be thetransceiver unit 710). Further, the processor 11, the memory 12, theinput port 13, and the output port 14 may communicate with each otherthrough an internal connection path, to transfer a control signal and/ora data signal. The memory 12 is configured to store a computer program,and the processor 11 may be configured to invoke and run the computerprogram in the memory 12. The memory 12 may be integrated into theprocessor 11, or may be disposed separately from the processor 11.

Optionally, if the communication device 900 is a terminal device, theinput port 13 is a receiver, and the output port 14 is a transmitter.The receiver and the transmitter may be one physical entity or differentphysical entities. When being one physical entity, the receiver and thetransmitter may be collectively referred to as a transceiver.

Optionally, if the communication device 900 is a chip or a circuit, theinput port 13 is an input interface, and the output port 14 is an outputinterface.

In an implementation, functions of the input port 13 and the output port14 may be implemented by using a transceiver circuit or aspecial-purpose transceiver chip. The processor 11 may be implemented byusing a special-purpose processing chip, a processing circuit, aprocessor, or a general-purpose chip.

In another implementation, the terminal device provided in thisembodiment of this application may be implemented by using ageneral-purpose computer. To be specific, program code for implementingfunctions of the processor 11, the input port 13, and the output port 14is stored in the memory 12, and the general-purpose processor executesthe code in the memory 12 to implement the functions of the processor11, the input port 13, and the output port 14.

The processor is mainly configured to process a communication protocoland communication data, control the entire terminal device, execute asoftware program, and process data of the software program, for example,configured to perform codebook fallback for a first codebook when firstdownlink information in a time unit subset meets a preset condition. Thememory is mainly configured to store a software program and data, forexample, store the first codebook described in the foregoingembodiments.

For ease of description, FIG. 10 shows only one memory and oneprocessor. In an actual terminal device, there may be a plurality ofprocessors and a plurality of memories. The memory may also be referredto as a storage medium, a storage device, or the like. This is notlimited in this embodiment of this application.

In an optional implementation, the processor may include a basebandprocessor and a central processing unit. The baseband processor ismainly configured to process a communication protocol and communicationdata, and the central processing unit is mainly configured to controlthe entire terminal device, execute a software program, and process dataof the software program.

Functions of the baseband processor and the central processing unit areintegrated into the processor in FIG. 10 . The baseband processor andthe central processing unit may alternatively be independent processorsconnected to each other by using technologies such as a bus.

The terminal device may include a plurality of baseband processors toadapt to different network standards, the terminal device may include aplurality of central processing units to enhance a processing capabilityof the terminal device, and components of the terminal device may beconnected to each other by using various buses. The baseband processormay alternatively be expressed as a baseband processing circuit or abaseband processing chip. The central processing unit may alternativelybe expressed as a central processing circuit or a central processingchip. A function of processing a communication protocol andcommunication data may be built into the processor, or may be stored ina storage unit in a form of a software program. The processor executesthe software program to implement a baseband processing function.

For example, in this embodiment of this application, an antenna havingsending and receiving functions and a control circuit may be consideredas the transceiver unit 710 of the communication device 700, and aprocessor having a processing function may be considered as theprocessing unit 720 of the communication device 700. As shown in FIG. 8, the communication device 700 includes the transceiver unit 710 and theprocessing unit 720. The transceiver unit may alternatively be referredto as a transceiver, a transceiver communication device, or the like.Optionally, a component, configured to implement a receiving function,in the transceiver unit 710 may be considered as a receiving unit, and acomponent, configured to implement a sending function, in thetransceiver unit 710 may be considered as a sending unit. In otherwords, the transceiver unit 710 includes a receiving unit and a sendingunit. For example, the receiving unit may also be referred to as areceiver, a receiver circuit, or the like, and the sending unit may bereferred to as a transmitter, a transmit circuit, or the like.

FIG. 11 is a schematic block diagram of a communication device 1000according to another embodiment of this application. As shown in FIG. 11, the communication device 1000 may be a network device, or may be achip or a circuit, for example, a chip or a circuit that may be disposedin a network device. The network device corresponds to the networkdevice in the foregoing method.

The communication device 1000 may include a processor 31 (which may bethe processing unit 820) and a memory 32. The memory 32 is configured tostore an instruction, and the processor 31 is configured to execute theinstruction stored in the memory 32, so that the communication device1000 implements a step performed by the network device in the methodcorresponding to FIG. 4 .

The communication device 1000 may further include an input port 33(which may be the transceiver unit 810) and an output port 33 (which maybe the transceiver unit 810). Still further, the processor 31, thememory 32, the input port 33, and the output port 34 may communicatewith each other through an internal connection path, to transfer acontrol signal and/or a data signal. The memory 32 is configured tostore a computer program, and the processor 31 may be configured toinvoke and run the computer program in the memory 32, so as to controlthe input port 33 to receive a signal and control the output port 34 tosend the signal, to complete the step performed by the network device inthe method in FIG. 4 . The memory 32 may be integrated into theprocessor 31, or may be disposed separately from the processor 31.

The processor 31 controls the input port 33 to receive a signal andcontrols the output port 34 to send the signal, to complete the stepperformed by the network device in the foregoing method. The memory 32may be integrated into the processor 31, or may be disposed separatelyfrom the processor 31.

Optionally, if the communication device 1000 is a network device, theinput port 33 is a receiver, and the output port 34 is a transmitter.The receiver and the transmitter may be one physical entity or differentphysical entities. When being one physical entity, the receiver and thetransmitter may be collectively referred to as a transceiver.

Optionally, if the communication device 1000 is a chip or a circuit, theinput port 33 is an input interface, and the output port 34 is an outputinterface.

Optionally, if the communication device 1000 is a chip or a circuit,alternatively, the communication device 1000 may not include the memory32, and the processor 31 may read an instruction (a program or code)from a memory outside the chip, to implement functions of the networkdevice in the foregoing method corresponding to FIG. 4 .

In an implementation, functions of the input port 33 and the output port34 may be implemented by using a transceiver circuit or aspecial-purpose transceiver chip. The processor 31 may be implemented byusing a special-purpose processing chip, a processing circuit, aprocessor, or a general-purpose chip.

In another implementation, the device provided in this embodiment ofthis application may be implemented by using a general-purpose computer.To be specific, program code for implementing functions of the processor31, the input port 33, and the output port 34 is stored in the memory32, and the general-purpose processor executes the code in the memory toimplement the functions of the processor 31, the input port 33, and theoutput port 34.

In this embodiment of this application, FIG. 11 may be a schematicstructural diagram of a network device that can be configured toimplement the functions of the network device in the foregoing method.The processor 31 may implement functions of the processing unit 820 inthe communication device 800, and the input port 33 and the output port34 may implement functions of the transceiver unit 810 in thecommunication device 800. This is not limited in this application.

The feedback information transmission method in the foregoing embodimentof this application may be applied to the processor, or may beimplemented by the processor. The processor may be an integrated circuitchip and has a signal processing capability. In an implementationprocess, steps in the foregoing methods can be implemented by using ahardware integrated logical circuit in the processor, or by usinginstructions in a form of software. The processor may be a generalpurpose processor, a digital signal processor (DSP), anapplication-specific integrated circuit (ASIC), a field programmablegate array (FPGA) or another programmable logic device, a discrete gateor a transistor logic device, a discrete hardware component, a system onchip (SoC), a central processing unit (CPU), a network processor (NP), adigital signal processing circuit (DSP), a micro controller unit (MCU),a programmable logic device (PLD), or another integrated chip. Theprocessor may implement or perform the methods, the steps, and logicalblock diagrams that are disclosed in the embodiments of thisapplication. The general-purpose processor may be a microprocessor, orthe processor may be any conventional processor, or the like. Steps ofthe methods disclosed with reference to the embodiments of thisapplication may be directly executed and accomplished by using ahardware decoding processor, or may be executed and accomplished byusing a combination of hardware and software modules in the decodingprocessor. A software module may be located in a mature storage mediumin the art, such as a random access memory (RAM), a flash memory, aread-only memory (ROM), a programmable read-only memory, an electricallyerasable programmable memory, a register, or the like. The storagemedium is located in the memory, and the processor reads instructions inthe memory and completes the steps in the foregoing methods incombination with hardware of the processor.

It can be understood that when the embodiments of this application areapplied to a chip in a network device, the chip in the network deviceimplements functions of the network device in the foregoing methodembodiments. The chip in the network device receives an uplink sharedchannel and the uplink data from another module (for example, a radiofrequency module or an antenna) in the network device. The uplink sharedchannel and the uplink data are sent by a terminal device to a basestation.

When the embodiments of this application are applied to a chip in aterminal device, the chip in the terminal device implements functions ofthe terminal device in the foregoing method embodiments. The chip in theterminal device sends the uplink control information from another module(for example, a radio frequency module or an antenna) in the terminaldevice, where the uplink control information carries the first codebook.

All or some of the foregoing embodiments may be implemented throughsoftware, hardware, firmware, or any combination thereof. When softwareis used to implement the embodiments, the foregoing embodiments may beimplemented completely or partially in a form of a computer programproduct. The computer program product includes one or more computerinstructions or computer programs. When the program instructions or thecomputer programs are loaded and executed on a computer, the proceduresor functions according to the embodiments of this application are all orpartially generated. The computer may be a general-purpose computer, aspecial-purpose computer, a computer network, or another programmablecommunication device. The computer instructions may be stored in acomputer-readable storage medium or may be transmitted from onecomputer-readable storage medium to another computer-readable storagemedium. For example, the computer instructions may be transmitted fromone website, computer, server, or data center to another website,computer, server, or data center in a wired manner or through aninfrared, radio, or microwave manner. The computer-readable storagemedium may be any usable medium accessible by a computer, or a datastorage device, such as a server or a data center, integrating one ormore usable media. The usable medium may be a magnetic medium (forexample, a floppy disk, a hard disk, or a magnetic tape), an opticalmedium (for example, a DVD), a semiconductor medium, or the like. Thesemiconductor medium may be a solid-state drive.

It should be understood that the term “and/or” in this specificationdescribes only an association relationship for describing associatedobjects and represents that three relationships may exist. For example,A and/or B may represent the following three cases: Only A exists, bothA and B exist, and only B exists. In addition, the character “/” in thisspecification generally indicates an “or” relationship between theassociated objects.

It should be understood that sequence numbers of the foregoing processesdo not mean execution sequences in various embodiments of thisapplication. The execution sequences of the processes should bedetermined according to functions and internal logic of the processes,and should not be construed as any limitation on the implementationprocesses of the embodiments of this application.

The units and algorithm steps in the examples described with referenceto the embodiments disclosed in this specification may be implemented byelectronic hardware or a combination of computer software and electronichardware. Whether the functions are performed by hardware or softwaredepends on particular applications and design constraints of thetechnical solutions. A different method may be used to implement thedescribed functions for each particular application, but it should notbe considered that the implementation goes beyond the scope of thisapplication.

For convenient and brief description, for a detailed working process ofthe foregoing system, communication device, or unit, reference may bemade to a corresponding process in the foregoing method embodiments, andno more details are described herein again.

In the several embodiments provided in this application, it should beunderstood that the disclosed system, communication device, and methodmay be implemented in other manners. For example, the describedcommunication device embodiments are merely examples. For example, theunit division is merely logical function division and may be otherdivision in actual implementation. For example, a plurality of units orcomponents may be combined or integrated into another system, or somefeatures may be ignored or may be not performed. In addition, thedisplayed or discussed mutual couplings or direct couplings orcommunication connections may be indirect couplings or communicationconnections through some interfaces, communication devices, or units,and may be implemented in electrical, mechanical, or other forms.

The units described as separate parts may or may not be physicallyseparate. Parts displayed as units may or may not be physical units, andmay be located in one position or distributed on a plurality of networkunits. Some or all of the units may be selected based on actualrequirements to achieve the objectives of the solutions of theembodiments.

In addition, functional units in the embodiments of this application maybe integrated into one processing unit, or each of the units may existalone physically, or two or more units are integrated into one unit.

When the functions are implemented in the form of a software functionalunit and sold or used as an independent product, the functions may bestored in a computer-readable storage medium. Based on such anunderstanding, the technical solutions of this application essentially,or the part contributing to the prior art, or some of the technicalsolutions may be implemented in a form of a software product. Thesoftware product is stored in a storage medium, and includes severalinstructions for instructing a computer device (which may be a personalcomputer, a server, or an apparatus) to perform all or some of the stepsof the methods described in the embodiments of this application. Theforegoing storage medium includes any medium that can store programcode, such as a USB flash drive, a removable hard disk, a read-onlymemory (ROM), a random access memory (RAM), a magnetic disk, or anoptical disc.

The foregoing descriptions are merely specific implementations of thisapplication, but are not intended to limit the protection scope of thisapplication. Any variation or replacement that can be readily figuredout within the technical scope disclosed in this application shall fallwithin the protection scope of this application. Therefore, theprotection scope of this application shall be subject to the protectionscope of the claims.

What is claimed is:
 1. A feedback information transmission method,comprising: obtaining, by a terminal device, a first associationrelationship between a time unit set comprising one or more first timeunits and a second time unit, wherein the one or more first time unitsis for transmitting one or more physical downlink shared channels(PDSCHs), and wherein the second time unit is for transmitting feedbackinformation associated with the one or more PDSCHs; receiving, by theterminal device, from a network device, a first physical downlinkcontrol channel (PDCCH) which schedules a first PDSCH, wherein the firstPDCCH carries timing indication information indicating a timingrelationship between a time unit carrying the first PDSCH and the secondtime unit; receiving, by the terminal device, at least one PDSCH of theone or more PDSCHs from the network device, wherein the at least onePDSCH includes the first PDSCH; determining, by the terminal device, thesecond time unit according to the timing indication information;determining, by the terminal device, according to the first associationrelationship and the timing indication information, a second associationrelationship between a subset of the time unit set and the second timeunit, wherein the subset of the time unit set comprises at least onetime unit carrying the received at least one PDSCH; determining, by theterminal device, a first codebook according to feedback informationassociated with the received at least one PDSCH; and sending, by theterminal device, uplink control information including the first codebookin the second time unit, wherein the first codebook is determinedaccording to a preset condition, and the preset condition comprises afirst condition wherein, the first codebook includes only feedbackinformation associated with the first PDSCH carried in the one or morefirst time units that belong to the subset of the time unit set inresponse to the second association relationship comprising only anassociation relationship between the time unit carrying the first PDSCHand the second time unit.
 2. The method according to claim 1, whereinthe preset condition further comprises a second condition, and thesecond condition is that a value of downlink assignment indicator (DAI)for dynamically scheduling the first PDSCH is
 1. 3. The method accordingto claim 1, wherein the preset condition further comprises a thirdcondition, and the third condition is that the first PDSCH is carried ina primary frequency domain unit or a first secondary frequency domainunit in one or more frequency domain units configured for the terminaldevice.
 4. The method according to claim 1, wherein based on the firstcondition not being met, the first codebook includes feedbackinformation corresponding to all PDSCHs received in all first time unitsin the time unit set.
 5. The method according to claim 1, wherein thefirst association relationship is predefined; or the first associationrelationship is configured for the terminal device by the network devicevia radio resource control (RRC) signaling.
 6. The method according toclaim 1, further comprising: determining, by the terminal device, asemi-persistent codebook mode from a plurality of candidate codebookmodes, wherein the plurality of candidate codebook modes comprise thesemi-persistent codebook mode and a dynamic codebook mode.
 7. The methodaccording to claim 1, wherein the first PDCCH is a control channel forfallback scheduling.
 8. The method according to claim 7, wherein thecontrol channel for fallback scheduling has at least one of thefollowing characteristics: the control channel for fallback schedulingis used for data scheduling performed before a radio resource control(RRC) connection is established; or none of values of fields in thecontrol channel for fallback scheduling is configured by using RRCdedicated signaling.
 9. A communication apparatus comprising: a memoryconfigured to store a computer program; and a processor configured toexecute the computer program stored in the memory, to enable thecommunication apparatus to: obtain a first association relationshipbetween a time unit set comprising one or more first time units and asecond time unit, wherein the one or more first time units is fortransmitting one or more physical downlink shared channels (PDSCHs), andwherein the second time unit is for transmitting feedback informationcorresponding to the one or more PDSCHs; receive, from a network device,a first physical downlink control channel (PDCCH) that schedules a firstPDSCH, wherein the first PDCCH comprises timing indication informationindicating a timing relationship between a time unit carrying the firstPDSCH and the second time unit; receive at least one PDSCH of the one ormore PDSCHs from the network device, wherein the at least one PDSCHincludes the first PDSCH; determine the second time unit according tothe timing indication information; determine, according to the firstassociation relationship and the timing indication information, a secondassociation relationship between a subset of the time unit set and thesecond time unit, wherein the subset of the time unit set comprises atleast one time unit carrying the received at least one PDSCH; determinea first codebook according to feedback information associated with thereceived at least one PDSCH; and send uplink control informationincluding the first codebook in the second time unit, wherein the firstcodebook is determined according to a preset condition, and the presetcondition comprises a first condition where, the first codebook includesonly feedback information associated with the first PDSCH in response tothe second association relationship comprising only an associationrelationship between the time unit carrying the first PDSCH and thesecond time unit.
 10. The apparatus according to claim 9, wherein thepreset condition further comprises a second condition, and the secondcondition is that a value of downlink assignment indicator (DAI) fordynamically scheduling the first PDSCH is
 1. 11. The apparatus accordingto claim 9, wherein the preset condition further comprises a thirdcondition, and the third condition is that the first PDSCH is carried ina primary frequency domain unit or a first secondary frequency domainunit in one or more frequency domain units configured for the apparatus.12. The apparatus according to claim 9, wherein based on the firstcondition not being met, the first codebook includes feedbackinformation corresponding to all PDSCHs received in all first time unitsin the time unit set.
 13. The apparatus according to claim 9, whereinthe first association relationship is predefined; or the firstassociation relationship is configured for the apparatus by the networkdevice via radio resource control (RRC) signaling.
 14. The apparatusaccording to claim 9, wherein the computer program further enables theapparatus to: determine a semi-persistent codebook mode from a pluralityof candidate codebook modes, wherein the plurality of candidate codebookmodes comprise the semi-persistent codebook mode and a dynamic codebookmode.
 15. The apparatus according to claim 9, wherein the first PDCCH isa control channel for fallback scheduling.
 16. The apparatus accordingto claim 15, wherein the control channel for fallback scheduling has atleast one of the following characteristics: the control channel forfallback scheduling is used for data scheduling performed before a radioresource control (RRC) connection is established; or none of values offields in the control channel for fallback scheduling is configured byusing RRC dedicated signaling.
 17. A communication apparatus comprising:a memory configured to store a computer program; and a processorconfigured to execute the computer program stored in the memory, toenable the communication apparatus to: obtain a first associationrelationship between a time unit set comprising one or more first timeunits and a second time unit, wherein the one or more first time unitsis for transmitting one or more physical downlink shared channels(PDSCHs), and wherein the second time unit is for transmitting feedbackinformation associated with the one or more PDSCHs; send a firstphysical downlink control channel (PDCCH) that schedules a first PDSCHto a terminal device, wherein the first PDCCH comprises timingindication information indicating a timing relationship between a timeunit carrying the first PDSCH and the second time unit; send at leastone PDSCH of the one or more PDSCHs, wherein the at least one PDSCHincludes the first PDSCH; determine the second time unit according tothe timing indication information; and receive, in the second time unit,uplink control information from the terminal device, wherein the uplinkcontrol information includes a first codebook determined according tofeedback information associated with the received at least one PDSCH,and wherein the first codebook is determined according to a presetcondition, and the preset condition comprises a first condition wherethe first codebook includes only feedback information associated withthe first PDSCH in response to a second association relationshipcomprising only an association relationship between the time unitcarrying the first PDSCH and the second time unit, wherein the secondassociation relationship between a subset of the time unit set and thesecond time unit is determined according to the first associationrelationship and the timing indication information, and wherein thesubset of the time unit set comprises at least one time unit carryingthe received at least one PDSCH.
 18. The apparatus according to claim17, wherein the preset condition further comprises a second condition,and the second condition is that a value of downlink assignmentindicator (DAI) for dynamically scheduling the first PDSCH is
 1. 19. Theapparatus according to claim 17, wherein the preset condition furthercomprises a third condition, and the third condition is that the firstPDSCH is carried in a primary frequency domain unit or a first secondaryfrequency domain unit in one or more frequency domain units configuredfor the terminal device.
 20. The apparatus according to claim 17,wherein based on the first condition not being met, the first codebookincludes feedback information corresponding to all PDSCHs received inall first time units in the time unit set.
 21. The apparatus accordingto claim 17, wherein the computer program further enables the apparatusto: determine a semi-persistent codebook mode from a plurality ofcandidate codebook modes, wherein the plurality of candidate codebookmodes comprise the semi-persistent codebook mode and a dynamic codebookmode; and configure the semi-persistent codebook mode for the terminaldevice via signaling.